~emersion/soju#207: 
Duplicated upstream connection due to race

  1. connectToUpstream called, takes some time
  2. User sends net update to the service
  3. network.stop is called, but net.conn == nil because the connection from step (1) is still being established
  4. connectToUpstream is called a second time and succeeds
  5. The connection initiated in step (1) finally succeeds
Status
REPORTED
Submitter
~emersion
Assigned to
No-one
Submitted
a month ago
Updated
a month ago
Labels
bug upstream

~emersion added bug a month ago

~emersion added upstream a month ago

Register here or Log in to comment, or comment via email.