Non-blocking sockets report EAGAIN as a hard failure
On a busy write the socket returns EAGAIN and the engine logs it as a failed create and moves on, when it should just retry the non-blocking write. Cost me a name I'm fairly sure was catchable.
On a busy write the socket returns EAGAIN and the engine logs it as a failed create and moves on, when it should just retry the non-blocking write. Cost me a name I'm fairly sure was catchable.
0 comments
Sign in with your TDesk account to comment.