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
The server.stop call does three things without any synchronization:
sends out a bye
stops the advertise loop
closes sockets
The trouble is that _stop (closing sockets) is called without waiting for _send's callback to complete. So you will see the 'Sending a message to %s:%s' from _send, but you will don't see the 'Outgoing server message' from the completion in advertise. If I put a breakpoint before _stop, this message usually makes it out when I run.
I'm on win 10 with multiple NICs
The text was updated successfully, but these errors were encountered:
The server.stop call does three things without any synchronization:
sends out a bye
stops the advertise loop
closes sockets
The trouble is that _stop (closing sockets) is called without waiting for _send's callback to complete. So you will see the 'Sending a message to %s:%s' from _send, but you will don't see the 'Outgoing server message' from the completion in advertise. If I put a breakpoint before _stop, this message usually makes it out when I run.
I'm on win 10 with multiple NICs
The text was updated successfully, but these errors were encountered: