-
Notifications
You must be signed in to change notification settings - Fork 446
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
Already piped error #244
Comments
@ajayrao80 do you have a stacktrace of the error? Also, what version of |
Here's the stack trace:
Also, I know why it's happening. Once the node connects with another node, and if one of them goes offline, and when they come back they try to connect again. But because they were connected before it throws an error. Is there any way to handle that? I tried putting the entire dial thing on try catch block, it didn't work. |
[email protected] should catch this error. Can you try updating your package lock? I'm working on a release for libp2p-switch to upgrade to 0.14.3 explicitly. That is good to know! I'm also currently working on making libp2p-switch a full state machine, I will see if I can include a root resolution for this issue there. In the mean time [email protected] should catch the throw. |
Thanks! That worked!! |
Type: Bug
Severity: Low
Description: Occasionally I get already piped error. I have no idea what it is and why it occurs. I thought it has something to do with dialing and tried catching it but I failed.
Can anyone please explain what it is and how to get around it
The text was updated successfully, but these errors were encountered: