You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
a node operator on Kiwi News always reports the following error:
We don't know where this is coming from, but we think it is libp2p. Before opening an issue, I asked in the libp2p TG if someone could help us find the cause of this, but it was suggested that I open an issue: https://t.me/c/2109810685/11/818
Severity: Critical because it makes our application panic
Description: This happens once two nodes are connected and exchanging messages. If one of the nodes unexpectedly crashes or gets terminated, then the other one will throw this error. I have checked most/all interactions I have with libp2p methods to make sure I'm try catching everything, but I haven't managed to find where this error is coming from. And also: the error doesn't have a stack trace, so I'm also unsure how I'd anyways find out more.
Steps to reproduce the error: Run two Kiwi News nodes, wait until they start the set reconciliation. Kill one node with Ctrl - C. Most likely the other will throw the ECONNRESET.
The text was updated successfully, but these errors were encountered:
Hi,
a node operator on Kiwi News always reports the following error:
We don't know where this is coming from, but we think it is libp2p. Before opening an issue, I asked in the libp2p TG if someone could help us find the cause of this, but it was suggested that I open an issue: https://t.me/c/2109810685/11/818
Version: We use libp2p v0.40.0 https:/attestate/kiwistand/blob/41aa70347eb8786f1cefa6746aa700a563c053c1/package.json#L83 we don't really have budget to upgrade this ATM
Platform: Ubuntu
Subsystem: I'm not sure. But we use a variety of libp2p packages where this could originate from, see this part of the package.json: https:/attestate/kiwistand/blob/41aa70347eb8786f1cefa6746aa700a563c053c1/package.json#L47-L55
Severity: Critical because it makes our application panic
Description: This happens once two nodes are connected and exchanging messages. If one of the nodes unexpectedly crashes or gets terminated, then the other one will throw this error. I have checked most/all interactions I have with libp2p methods to make sure I'm try catching everything, but I haven't managed to find where this error is coming from. And also: the error doesn't have a stack trace, so I'm also unsure how I'd anyways find out more.
Steps to reproduce the error: Run two Kiwi News nodes, wait until they start the set reconciliation. Kill one node with Ctrl - C. Most likely the other will throw the ECONNRESET.
The text was updated successfully, but these errors were encountered: