UDP engine aborts on networking-related errors from socket syscalls #2862 #3638
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bluca
reviewed
Aug 22, 2019
|
please add a relicense statement, and fix the formatting error that the CI is showing |
…eromq#2862 (remove unused function)
I had fixed the formatting of udp_engine.cpp in fe2287d (by |
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This refactoring is supposed to prevent ZeroMQ from terminating upon UDP engine tuning errors (in
zmq::udp_engine_t::plug). As far as I was able to figure out, the session will terminate silently onprotocol_error, which isn't good, probably. Not really sure, where to go from here...