Repository navigation
fix: retain safe U03 cancellation failure diagnostics - #280
Merged
Merged
Conversation
DavidHLP
marked this pull request as ready for review
October 11, 2026 14:36
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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
1 participant
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.
U03 cancellation acceptance stopped at a failed thread-state read, but its recorded reason omitted the HTTP status and Result code. Retain those two numeric values in the failure reason so the next observed failure can distinguish protocol and upstream responses without exposing response bodies, messages, reasons, or trace IDs. The failure remains a failure; cancellation assertions and acceptance rules are unchanged.
Validation: two regressions failed on the prior generic reason at 7fe6ccd. Exact227dbb146 remote focused verification passed82 tests and independent review approved. Current-head CI38147946442 completedSUCCESS. The zero-paid reproduction against real Java authentication passed concurrent state reads, cancellation, and late-result fencing; this does not establish the cause of the historical paid U03 failure or constitute formal acceptance.
Historical V16 U02 PASS and U03 INCOMPLETE records remain bound to f14cc4e. V16 settled 104 calls / 35,977 microUSD with no new unknown or unsettled usage; the three historical unknown liabilities remain retained. U03/U04 and parent delivery remain incomplete.