UDP engine aborts on networking-related errors from socket syscalls (2) #2862 #3640
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Follow-up for UDP send/receive. Also updated
plug
function to terminate session only whensetsockopt
failed, and request reconnection otherwise. Still haven't looked into how socket monitoring events work, so error handling happens silently.Note that I added EAGAIN/EWOULDBLOCK and EPIPE in the list of "recoverable" errors.