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
Reliably see this when using mplex when a remote peer disconnects (possibly w/o warning):
DEBUG mplex unavailable while waiting for incoming: failed to read the header correctly from the underlying connection: {'requested_count': 2, 'received_count': 0}
The text was updated successfully, but these errors were encountered:
There seems to be race between our set of peers and the pubsub machinery.
If a peer disconnects at the right time (which seems to be when pubsub is iterating through peers to send messages to), the peers dictionary is changed, which raises an iterator exception.
Reliably see this when using
mplex
when a remote peer disconnects (possibly w/o warning):The text was updated successfully, but these errors were encountered: