-
Notifications
You must be signed in to change notification settings - Fork 185
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
fix(iroh-relay): removes deadlock in Clients
#3099
Conversation
Also downgrades "stream terminated" from a `warn` to a `trace`, so we don not get an warning everytime a connection to the relay closes
Documentation for this PR has been generated and is available at: https://n0-computer.github.io/iroh/pr/3099/docs/iroh/ Last updated: 2025-01-07T18:24:43Z |
Can confirm this fixes the issue for me. |
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.
LGTM but let's wait for @dignifiedquire as he wrote this I think
Okay, added a The thing that really sold it for me was that it is now easy for this deadlock to show up in a test if there are future refactors. It will be difficult to explicitly remove the |
Description
Remove the deadlock that was a bit hidden due to
DashMap
.Added
client
parameter tounregister
to explicitly drop before attempting to call into theclients
DashMap
again.Notes & open questions
The
warn
log for stream termination seems a little fear-mongering, but I'm not sure the best way to "downgrade" this, as we seem to rely on this error in tests likeendpoint_relay_connect_loop
. Ended up leaving it as is.Change checklist