Repository navigation
Isolate slow UDP targets with bounded per-target send queues - #54
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.
Changes
Evidence
766d090with the frozen four-test wire fixture: direct concurrent H3 passed; native, H3-through-SOCKS and auto-H3-through-SOCKS failed warm-target progress while another target's resolver was held. Recovery and cleanup controls completed.make check: 16 test-bearing Go packages and 49 release-helper Python tests, plus formatting/module/boundary/notice/vet gates.make race: all 16 test-bearing Go packages passed.Boundaries
Native
UDPReceiveQueuenow counts active plus waiting packets (previously waiting plus one active). Per-target half-budget caps intentionally shed overload; this is not universal fairness, reliable UDP delivery or ordering across different keys/DNS aliases. Custom concurrent packet providers must honor cancellation/Close.No protocol, authentication, dependency, default transport, version or release changes. No browser-equivalence or traffic-identification claim; no canceled large corpus or old remote machine was reused.