fix(x402): preserve handled failures after waiter cancellation - #18
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.
Summary
Fix Python 3.14 exception diagnostics after a caller cancels an x402 capability refresh or a prepared-payment wait. The shared operation can still fail after cancellation; that error remains handled by the SDK and available to other callers.
Use the same shared-task waiting pattern as TAP verification, without changing payment requests, approval cancellation, cache lifetimes, or hook execution. Leave bounded approval cleanup unchanged.
Verification
No public API, dependency, version, or release changes.