~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
RESOLVED CLOSED
Submitter
~emersion
Assigned to
No-one
Submitted
1 year, 26 days ago
Updated
8 months ago
Labels
bug upstream

~emersion REPORTED CLOSED 10 months ago

Simon Ser referenced this ticket in commit ac16729.

~emersion 8 months ago

Simon Ser referenced this ticket in commit 55c75a0.

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