Fix crashes on HTTPServer's SIGPIPE #1130
Merged
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.
Case in point
Working on a project of my own that uses Livestreamer, I stumbled upon an issue while using the
--player-external-http
optionBasically, if a socket sends an HTTP request and closes before Livestreamer's HTTP server sends the response, consequent calls to
send
on the socket will send aSIGPIPE
to Livestreamer's process which will raise asocket.error
exception that was currently not caught.Possible environment to reproduce
For example, running this command:
Followed by this little script:
Will make the first command crash after a short time with an output like:
Resolution
I just added a
try-except
block around the code that was callingsend
on the client's socket and forwarded the exception as anOSError
Those are ignored at an upper level in the call stack so no more crashes