Repository navigation
fix(tunnel): preserve H3 opening cancellation at stream handoff - #51
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
Evidence
Four new terminal regression scenarios first failed against unchanged main production under Go 1.25.13 race, with the intended failures and healthy controls continuing: TCP/UDP returned live streams after post-proof cancellation; UDP response waits lost private cancellation and deadline causes. Frozen fixtures then passed:
Independent source/fixture reviews found no must-fix.
Tests exercise real verified TLS/H3 proof, request cleanup, an existing TCP sibling, subsequent complete TCP/UDP echoes on the same physical connection with one full credential, and cancellation detached after successful handoff.
Limits
The final-lock recheck is source-order defense, not a separately reproduced lock-wait race. UDP stream-open/header-send error paths are reviewed but not individually fault-injected. Send has no per-call context; its lazy UDP opening uses an internal association-owned budget. No remote host, formal corpus/browser comparison or passive-equivalence claim. Published v1.0.1 binaries are unchanged.