-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
websocket: failed to close network connection: close tcp #10416
Comments
Can someone give more context about the criticality of this issue, please? |
This bug here seems to be obnoxious logging rather than some other underlying issue. It's going to be reverted in the next go-libp2p release (and will get propagated into the following kubo release) libp2p/go-libp2p#2762. |
I built the error with docker. You can try it.
If I need to provide detailed information, it will be a few days later.
2024 年 5 月 6 日星期一 20:04, pablomendezroyo ***@***.***(mailto:2024 年 5 月 6 日星期一 20:04, pablomendezroyo <<a href=)> 来信:
… Can someone give more context about the criticality of this issue, please?
—
Reply to this email directly, [view it on GitHub](#10416 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AUUI7W5YLLU6TNNIT5FMV5TZA5WVNAVCNFSM6AAAAABHHBVFMOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJVHA2TONZZGM).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
This should be fixed in v0.29 |
Not fixed yet, still have the bug. |
Indeed, the upstream project had some hiccups. |
Still faced this issue when using Kubo (containerized in version 0.29.0-3f0947b). |
Checklist
Installation method
ipfs-desktop
Version
No response
Config
No response
Description
The text was updated successfully, but these errors were encountered: