-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Dcutr panics with low connection limits #2906
Comments
Thanks for reporting this panic @dariusc93. The root of the issue is here: Line 538 in 2c739e9
When we hit the connection limit, we report the issue to the If I am not mistaken the patch for this panic would be simply: - self.behaviour.inject_dial_failure(None, handler, &error);
+ self.behaviour.inject_dial_failure(peer_id, handler, &error); @dariusc93 could you validate the above and propose a patch in case it resolves your issue? |
Thanks for the response @mxinden, I did try that and it did resolve the panic I was getting with a low limit (which also allow the logs to see the error too) |
@dariusc93 want to create a pull request? 😇 |
Sorry @mxinden been busy so i forgot to create it. Will do that in just a bit! |
Given that #2928 is merged I am closing here. Thanks @dariusc93! |
Summary
Receives a panic from dcutr when connecting to another peer
This seems to happen when using the following
ConnectionLimit
for swarm.https://github.com/dariusc93/libp2p-chat-test/blob/bugged/dcutr-behaviour-rs-154-35/src/behaviour.rs#L175-L181
Thought it was related to a separate project I was working on but wanted to isolate it first to try to reproduce it with just libp2p. It does seem to do better with limits set to 512 or more but hard to really determine if thats the case and scanning through the code doesnt really give a clear answer.
Expected behaviour
Not to panic when using dcutr with connection limits set low.
Actual behaviour
Panics sometime after swarm
Debug Output
Possible Solution
Version
Would you like to work on fixing this bug?
Maybe
The text was updated successfully, but these errors were encountered: