-
Notifications
You must be signed in to change notification settings - Fork 1
fix(storage): let crash-recovery finalize tolerate legitimate reclassification #3370
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
Sinity
merged 1 commit into
master
from
fix/interrupted-finalize-tolerates-reclassification-ewfp
Jul 28, 2026
Merged
Changes from all commits
Commits
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
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.
interrupted=Truedoes not exclusively identify recovery after an arbitrary gap:apply_raw_authority_frontierpasses it whenever any strategy returns a retryable outcome (raw_reconciler.py:1393-1399), while still finalizing in the same invocation. If a strategy fails after partially committing durable work—for example, browser-origin copy-forward commits its source stage before the separate index stage—this condition now suppresses the check that would detect the immutable plan disappearing or changing, and publishes the census as interrupted without creating the stale-plan blocker that previously kept the archive fail-closed. Use a distinct actual-recovery flag, or keep this invariant enabled for the ordinary apply caller even when its outcome is retryable.Useful? React with 👍 / 👎.