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
When we dial multiple addresses of the same peer, we set the same connection ID for all addresses.
The first successful connection is kept around, while the other pending connections are canceled.
Some thoughts and possible root causes:
I suspect there might be a race between canceling dials and when dials are reported as successful, with the side effect of generating multiple warnings, of similar addresses with the same connection id. All warnings share the same ConnectionId(2347695).
Part two of: #172
Detected during triaging of: paritytech/polkadot-sdk#5609
When we dial multiple addresses of the same peer, we set the same connection ID for all addresses.
The first successful connection is kept around, while the other pending connections are canceled.
Some thoughts and possible root causes:
ConnectionId(2347695)
.reject()
#198)The text was updated successfully, but these errors were encountered: