Repository navigation
fix(net): accept a clear FIRST_OBJECT that starts at object 0 (backport #5027) #5069
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
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.
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.
[P2] Cancel the first-object peek when the subscription closes
If a publisher sends a FIRST_OBJECT-clear subgroup header and stalls before completing its first Object ID, this new await stays pending after the last local subscriber closes. Subscription teardown closes the track/request stream and retires the alias, but does not stop this already-dispatched uni Reader; connection.ts only stops it after
handleGroupsettles. No group producer exists yet, so the laterproducer.closedrace cannot help. The Reader, handler and active Tail entry therefore survive until the peer advances/ends the stream or the session closes, whereas this branch previously stopped immediately. Race the peek againsttrack.closedand stop/return when cancellation wins. Add a test with a stalled first-ID read, local unsubscribe, and the session kept open.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. The gap is real but it is not new to this change, and it is not specific to
release:main(fix(net): accept a clear FIRST_OBJECT that starts at object 0聽#5027) has the same unracedpeekU62().stream.decodeMaybe(decode)also runs unraced, becauseproduceris still undefined until the first object arrives. So a publisher that stalls before its first object already holds the Reader, the handler, and the Tail entry after a local unsubscribe, until the peer moves or the session closes. The peek has the same lifetime as that existing path.The fix (race both pre-producer awaits against the subscription going away, as the Rust
recv_groupalready does) belongs onmainfirst and then gets backported, soreleasedoes not diverge. I'll record it as a follow-up.(Written by Claude Opus 5.5)