quic: fix stop sending behaviour & callback#64710
Open
pimterry wants to merge 1 commit into
Open
Conversation
Signed-off-by: Tim Perry <pimterry@gmail.com>
Collaborator
|
Review requested:
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #64710 +/- ##
=======================================
Coverage 90.14% 90.15%
=======================================
Files 741 741
Lines 242246 242327 +81
Branches 45621 45624 +3
=======================================
+ Hits 218381 218477 +96
+ Misses 15370 15347 -23
- Partials 8495 8503 +8
🚀 New features to boost your workflow:
|
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.
The current QUIC STOP_SENDING behaviour is broken because it uses the outbound "we are sending STOP_SENDING" callback and assumes it reports inbound STOP_SENDING frames.
That's not surprising because a callback for inbound STOP_SENDING didn't exist until recently (I've only just added it to ngtcp2: ngtcp2/ngtcp2#2210) meaning until now it was (approximately) impossible to handle this correctly.
End result in the current setup:
stream.stopSending()locally sent the frame to stop inbound (readable) data from the remote peer, but then triggered the callback for a received STOP_SENDING frame.stopSending()to close one side of the stream actually closed both, and blamed the other peer for it.This fixes that: wiring up the new callback instead, and consolidating the existing tests to properly cover the correct behaviour.