-
Notifications
You must be signed in to change notification settings - Fork 10
fix(stores): guard vector backfill against stale overwrites (ARN-216) #395
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
Draft
rita-aga
wants to merge
3
commits into
main
Choose a base branch
from
grok/arn-216-vector-backfill-race
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
163787e
test(server): failing DST for vector-backfill stale-overwrite race (A…
rita-aga b36c898
fix(stores): guard vector backfill against stale overwrites (ARN-216)
rita-aga d6d9e82
fix(store-postgres): non-wrapping i64 to u64 seq cast in vector guard…
rita-aga 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
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
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.
_loaded_seqis intentionally discarded here, leaving the key-index backfill with the exact same load-then-write race this PR fixes for vectors. The ADR (section "Consequences") documents this as a known residual: a stale upsert landing after a concurrent live key write will clobber the newer mapping, and the completion watermark will then treat the stale entry as authoritative. The impact is worse than the vector case — a wrong key mapping can route entity lookups to the wrong entity (or produce a false-absence hit) until the entity's next write corrects it. The ADR says a "Linear issue on reconnect" is tracked for the symmetric follow-up; confirming that issue exists and is prioritized before watermarking any type with key declarations would reduce the window this is exploitable.Prompt To Fix With AI