-
Notifications
You must be signed in to change notification settings - Fork 12
Real settle teardown, and peer settle-tuple reconciliation (settle teardown, step 3) #1076
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
+2,302
−287
Merged
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
03a29ba
feat: attach real settle teardown, and reconcile peer settle-tuple wr…
arul28 692175a
test: cover the residue table in the CRR-exclusion invariant
arul28 92426ea
fix: quality dual-review findings, including two blockers
arul28 5726321
fix: second-round review findings across teardown, reconcile and latency
arul28 44e2a62
fix: third-round review — the dedup guard was inert, and residue coul…
arul28 125f799
docs: correct settle claims that step 3 made false
arul28 aaf1e75
docs: record the sync bulk-settle shape as an open wire decision
arul28 410e990
fix: fourth-round findings — restore the worker pool, and stop over-c…
arul28 d499220
fix: stop the settle pool when a persistence failure propagates
arul28 86c4c5c
fix: honor stop_only everywhere, and see background jobs that outlive…
arul28 abec583
fix: gate the persisted background job on daemon liveness
arul28 df2aa0a
fix: make background-job liveness required and tri-state
arul28 b1fc48f
fix: scope the abort check to the window the teardown actually owns
arul28 9be4f22
fix: a hung provider stop is a timeout, not a rejection
arul28 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
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.
When a busy Pi session has queued follow-ups, settle teardown invokes this branch with
mode: "stop_only", butrt.pendingSteers.length = 0has already deleted those prompts before this new guard runs. Fresh evidence beyond the earlier comment is that the partial fix guards onlycancelQueuedSteers; the preceding direct queue clear remains unconditional, so Pi settles still irreversibly discard user input.Useful? React with 👍 / 👎.