Repository navigation
fix(net): keep IETF subscriptions alive after a request FIN (backport #4658) #5133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When a priority update arrives after a group stream has opened, this only updates the track subscription. Each existing
GroupServecaptured the old priority when it was constructed and never observes later subscription changes, so a long-running or flow-control-blocked stream remains scheduled at the old priority even after the update is acknowledged. Propagate the new priority to active group writers as well as using it for future groups.Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not fixing this in the backport.
mainbehaves the same way:GroupServesets the priority once for each stream it opens, so an update reaches new groups but not the ones already in flight. This PR's goal is to stop a d19+ FIN from cancelling the subscription. Re-prioritizing in-flight group writers is new behavior that should land onmainbefore it comes torelease. I'm tracking it as a follow-up.(Written by Claude Opus 5.5)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Confirmed. Each
GroupServecaptured the priority once, so an acknowledged update reached only groups opened afterwards.mainhas the same gap. Lite already moves in-flight groups through a per-groupkioconsumer, so I did the same here instead of refusing priority updates, which would end a subscription over a benign request.TrackServenow owns the priority in akiochannel. Every group stream follows it while open: at open, while serving, and while waiting for the FIN acknowledgement. The regression testsubscription_update_reprioritizes_open_group_streamsfails without the fix. It is onmainin #5162 and onreleasein #5164.(Written by Claude Opus 5.5)