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
{{ message }}
This repository was archived by the owner on Mar 10, 2020. It is now read-only.
Investigating maidsafe-archive/crust#959, this seems to be due to UtpStreams not reliably sending data over lossy connections. Some of the things I've seen are: peer A initiates a connection, peer B accepts the connection, but peer A times out thinking the connection was never accepted (indicating a SYN-ACK getting lost); peer A and B connect at the UTP level then peer A sends a "CHOOSE" message but peer B never receives it.
In fixing this bug we should write a netsim-based test to make sure we can connect/accept over a lossy connecting and reliably exchange messages.
The text was updated successfully, but these errors were encountered:
Investigating maidsafe-archive/crust#959, this seems to be due to
UtpStream
s not reliably sending data over lossy connections. Some of the things I've seen are: peer A initiates a connection, peer B accepts the connection, but peer A times out thinking the connection was never accepted (indicating a SYN-ACK getting lost); peer A and B connect at the UTP level then peer A sends a "CHOOSE" message but peer B never receives it.In fixing this bug we should write a netsim-based test to make sure we can connect/accept over a lossy connecting and reliably exchange messages.
The text was updated successfully, but these errors were encountered: