-
Notifications
You must be signed in to change notification settings - Fork 3.9k
fix(server): drop superseded tool updates from snapshots #5483
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
+277
−3
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
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.
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.
Dropped updates lose merged tool fields
High Severity
dropSupersededToolUpdatedActivitiesremovestool.updatedrows whenever a later matchingtool.completedexists, but clients only recover some completion fields by merging the prior update during collapse. When a completion omits payload data the update carried—for example MCPdata.item/toolData—snapshot reload drops that data and the work log no longer matches full-history resolution.Triggered by learned rule: Server-side activity pruning in projections must match client reader granularity and validity
Reviewed by Cursor Bugbot for commit 9d5aafd. Configure here.
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.
[claude-fable-5] RESPONDING ON BEHALF OF THEO
Verified empirically against the full real database before dismissing: replayed this exact drop over all 49,515
tool.updatedrows and diffed every one of the 36,577 dropped updates against its superseding completion for each field the clients' merge recovers (detail,title,command,data.item/toolData,kind,files,requestKind). Zero dropped rows carry any field their completion lacks — completions always ship a payload superset of their updates, including for MCP items. The scenario described (completion omittingdata.itemthe update carried) does not occur in practice. The projection's doc comment now records this verification.