-
Notifications
You must be signed in to change notification settings - Fork 115
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
Issues with Yamux / race-signal #554
Comments
@veermetri05 can you provide your full code or a reproduction repo? I am not seeing the error message you provided match up with the example code you gave in the issue description. |
Oops, seems like we needed more information for this issue, please comment with more details or this issue will be closed in 7 days. |
This issue was closed because it is missing author input. |
I have the same error. I had been using: "helia": "^5.0.0", "@chainsafe/libp2p-gossipsub": "^14.1.0", |
@silkroadnomad please open a small repro case if you can, and open a new issue so we can help you out |
@SgtPooki It seemed to have disappeared, but today I got it again. The issue is described here more accurately It seems related to WebRTC. I will disable WebRTC on the NodeJS Helia since it works mainly via tcp and wss right now. Lets see if I can do a simple repo for the issue to replicate. here my stacktrace and it also crashed NodeJS node completely (exited) |
@veermetri05 your transport shows you have only tcp enabled. Question is: How an issue could pop up in a WebRTC lib? Are you sure you only enabled tcp? Because I had webrtc and webrtc-direct enabled. Not properly configured, I must admit. |
To reproduce just create a Helia instance,
and run the program, wait for some time, then you get the issue.
The text was updated successfully, but these errors were encountered: