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
Fix TCP socket send() immediately back to back after connect() (#22630)
Previously, if an emulated TCP socket is connect()ed and one attempts to
send() back to back right after connecting, the send would fail because
the socket is not yet actually connected.
It is a bit hard to imagine where such behavior would be useful.
So this PR changes this behavior to be identical to how connectionless
UDP sockets are emulated: instead, connect() calls are always pretended
to succeed (since we cannot synchronously establish if the connect would
fail, so presume it'll work), and all send() calls that are issued while
the socket is connecting will be queued to be sent after the socket
actually connects.
0 commit comments