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
I have some program that panics while connected to gossip.
When i restart it, and get it to connect to one of its old peers it used to be connected to, i see ignoring connection: already accepted peer_id=PublicKey(…) origin=Accept.
Meanwhile, the node attempting to reconnect panics the task with the error: connection closed: connection lost.
This appears to happen because Gossip only wants to maintain one connection per pair, and I'd need to wait for the existing (broken) connection to time out.
It would be great to have an option to forcibly replace any existing connection when sending Command::JoinPeers from a node.
The text was updated successfully, but these errors were encountered:
I have some program that panics while connected to gossip.
When i restart it, and get it to connect to one of its old peers it used to be connected to, i see
ignoring connection: already accepted peer_id=PublicKey(…) origin=Accept.
Meanwhile, the node attempting to reconnect panics the task with the error:
connection closed: connection lost.
This appears to happen because Gossip only wants to maintain one connection per pair, and I'd need to wait for the existing (broken) connection to time out.
It would be great to have an option to forcibly replace any existing connection when sending
Command::JoinPeers
from a node.The text was updated successfully, but these errors were encountered: