Repository navigation
Correlate H3 authentication observations by request order - #55
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.
Fix
Test-only follow-up to #54. The first merged-main CI run 37093615860 failed in the minimum-Go authentication cancellation fixture; it was not rerun or represented as green.
The fixture treated post-handler completion order as request order. H3 response FIN can precede outer-handler observation, so two completed public echoes do not establish that ordering. An owned wire control holding only the first post-handler observer until the second was sent reproduced the identical
full/short=false/false, nonce=1, destination=2failure against the old collector. The original CI log lacks arrival ordinals, so it does not uniquely establish that schedule as its cause.[2,1].Validation
make checkandmake race: 16 test-bearing packages; 49 release-helper Python tests passed.Only one test file changes. No production, protocol, authentication, dependency, config, version or release changes. The first main failure and negative experiment remain separate retained evidence.