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: https://github.com/paritytech/litep2p/issues/172
Detected during triaging of: https://github.com/paritytech/polkadot-sdk/pull/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)
.