Repository navigation
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.
fix(code): name a generation before its commit, so a lost directory stays reclaimable #2096
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
base: master
Are you sure you want to change the base?
fix(code): name a generation before its commit, so a lost directory stays reclaimable #2096
Changes from all commits
b965a8e5d26c4c1072176File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
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.
[P1] Preserve reader-pinned generations after they leave current/previous
This set only covers the two generations in
current.json, while reader leases can keep older generations alive. On1072176ewith real embedded SeekDB, I reconstructed the old-writer crash state by pointing the current identifier's journal entry at a vanished staging name. Initial recovery correctly skips it. I then paused a public symbols query after it pinned that generation and ran threeindex(full=True)calls without changing the source. On the third recovery, the identifier is no longer in current/previous, so its database rows are deleted even though the original directory and reader lock still exist. The pending query returnsstatus="ok", the same fingerprint, anditems=[]instead ofrun.This occurs below the 64-entry window. The control with the journal naming its final directory keeps the rows and returns
run. Recovery must reconcile and protect all generations still held by readers before deleting an identifier from an older publication record.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.
Fixed in
5d26c4c9, before this round of review.interrupted_createintests/e2e/test_native_code_seekdb.pynow takes*args, **kwargsand forwards both, so thegeneration_idkeyword reachescreate()and the subprocess still stops at its pause marker.code-seekdb (3.11)and(3.14)both pass onccec4880.Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.