Repository navigation
fix(web): prevent user messages from vanishing on thread switch (#2409) #2498
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
6e9b17c
fix(web): prevent user messages from vanishing during safety-pipeline…
serrrfirat 2d611af
test(e2e): add Playwright tests for pending message persistence (#2409)
serrrfirat 83f4888
fix(e2e): use domcontentloaded for reload test — SSE blocks networkidle
serrrfirat 76c62f7
fix(web): address review — remove SSE early-clear race, use frequency…
serrrfirat 4536f15
fix(web): clear pending entry on turn completion — address henrypark1…
serrrfirat f2f727b
fix(web): address review — remove pending on send fail, Map for dedup…
serrrfirat 2f0b3ba
fix: remove unused imports in pending message test
serrrfirat 448e83c
ci: retrigger checks against updated staging base
serrrfirat e19af9b
fix(web): preserve images in pending messages, harden tests (#2498)
ilblackdragon File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The current implementation for re-injecting pending messages has a bug when a user sends the same message content multiple times in quick succession. By using a
SetfordbContents, you lose the frequency of each message. If a user sends "ok" and then "ok" again, andloadHistoryruns after the first one is persisted, theSetwill contain "ok". Both pending messages will then be considered "in the DB", and the second optimistic message will not be re-injected, causing it to vanish.Additionally, the logic can be refactored to be more DRY by calculating the
freshpending messages once and reusing the result.Here's a suggested implementation that addresses both points by using a frequency map for DB contents and simplifying the logic: