Repository navigation
fix(harness): order Terminal binding writes through End [SAP-3292] #1022
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
Closed
ynadge
wants to merge
1
commit into
assistant-history-review-fixes
from
terminal-binding-write-order
Closed
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| --- | ||
| "@sapiom/harness": patch | ||
| --- | ||
|
|
||
| Order Terminal binding writes with End and surface failed restart repairs. |
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
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.
🔴 Failed writes corrupt End snapshots
When a binding write fails during concurrent End,
subsessionBindingWriteQueuecan snapshot the failed caller's rollback.createReserveddeletes the marker before End's queued snapshot runs. The resulting tombstone lacks a marker, so the nextinit()rejects the registry as malformed.Learn more
The stored queue tail converts the active write's rejection into fulfillment. A later End write waits on that tail. When the active write rejects, the caller's catch can roll back memory before the later writer snapshots it.
createReserveddeletes its marker without checking whether End advanced the close generation;resumePreparedsimilarly restores the old marker. End has already added the session touserClosedSubsessions, andloadSubsessionBindingsrejects any closed ID without a marker.Example: A reserved create starts marker write A. End adds the closed tombstone and queues write B. Write A fails, so the create catch deletes the marker. Write B then snapshots
{ markers: {}, closedSessionIds: [id] }; the next launch rejects this file as malformed.Recommended fix: Make every binding rollback close-generation-aware, as
restartFreshPreparedalready does, so it cannot overwrite End's in-memory state. Add failure-and-End race tests for bothcreateReservedandresumeBound, including reloading the persisted registry.Was this helpful? React with 👍 or 👎 to provide feedback.