Repository navigation
Unify cancellation confirmation budget - #631
Merged
Merged
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A native cancellation that stops its subprocesses can still need more than ten seconds to confirm the native result and drain output. Apply one protocol-owned 30-second confirmation budget to Runtime settlement and cancellation receipts and to Core cancellation exchange/watchdog, returning immediately on confirmation or failure. Preserve the 15-second function acknowledgement and 10-second resource-close budgets; closing resources never converts failed settlement into an applied cancellation.
Validation: affected package tests, runtime contract gate, focused cancellation race tests, vet and EN/zh translation checks pass. Virtual-time coverage includes confirmation after the previous deadline, finite timeout, one native cancellation owner, output joins, Done/receipt ordering and earlier caller deadlines. Fresh independent complete-diff review found no in-scope defects. Database-dependent tests retained their prerequisite skips. Live Claude lifecycle qualification follows the integrated build; this is a reliability policy change, not a performance improvement.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.