-
Notifications
You must be signed in to change notification settings - Fork 317
fix(multipath): fix remote state actor termination #3676
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
Frando
merged 14 commits into
feat-multipath
from
Frando/mp-fix-remote-state-actor-loop
Nov 20, 2025
+70
−51
Merged
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
db9d18a
fix
Frando 08061e5
make nicer
Frando 3ee7c69
fix: check if local_addrs are connected
Frando 687d1fd
Merge remote-tracking branch 'origin/feat-multipath' into Frando/mp-f…
Frando 9c19639
chore: add log
Frando ab321af
chore: trace to debug for netsime
Frando 717ac88
fix: log failed addr in transports send
Frando 7c11665
fix: don't break RemoteStateActor if sending datagram fails
Frando 899df00
Simplify the idle timeout logic & don't short-circuit in `handle_msg_…
matheus23 e98b835
Merge remote-tracking branch 'origin/feat-multipath' into Frando/mp-f…
matheus23 2eeac07
fix: add error context add call site
Frando ff20fa3
chore: clippy
Frando 3f8d72a
Stop the `RemoteStateActor` when the direct addr watcher disconnects
matheus23 52d4382
Rename `local_addrs` to `local_direct_addrs`
matheus23 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.
So this was a poor-man's attempt at being able to have "fatal" errors. The right thing of course is to panic and spawn the tasks in a JoinSet and making sure the panic bubbles up to the endpoint. But that's for another day I guess. For now making this infallible is the safer approach I think. While if forces you to handle the fatal error everywhere it will probably result in better code.