Repository navigation
Recreate expired UDP sessions without losing the first datagram #108
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
SajjadPourali
merged 3 commits into
narrowlink:main
from
szonov:fix/udp-session-replacement
Nov 2, 2026
Merged
Changes from all commits
Commits
Show all changes
3 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
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.
I believe it would be better to close the stream in the drop prior to sending the destroy notification.
IpStackUdpStream::drop() sends its destroy notification before Rust drops its receiver field. On a multithreaded runtime, the watcher and stack loop can process that notification while the receiver is still open. The new is_closed() check then skips removal. Once destruction finishes, no further notification arrives
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.
Thanks, you're right: the notification could be handled before Rust drops the receiver field, causing the closed-sender guard to skip cleanup. Fixed in c3dc279 by closing the UDP receiver before sending the notification, as suggested.
Added a deterministic regression test that registers a custom waker on the destroy receiver and checks sender.is_closed() synchronously when the notification wakes it, before the destructor returns. It fails without close() and passes with it. The stale-notification guard remains in place to protect a live replacement.
Also merged current upstream main. On macOS arm64, all 52 unit tests and 23 documentation tests pass, along with formatting, Clippy for all targets/features with -D warnings, and the examples/tests build.