-
Notifications
You must be signed in to change notification settings - Fork 28
Handle server closing connection after response body is sent #223
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
991fc64
Handle EPIPE error when server unexpectedly closes the connection
JoshMock 120b3c6
Add tests for EPIPE server disconnect edge case
JoshMock 1a2f609
Drop irrelevant comment
JoshMock a1c7abb
Cleanup of unneeded logic
JoshMock 717ac1a
Explicitly handle EPIPE error
JoshMock 82ef905
Make error message check more permissive
JoshMock 7465395
Make error message check even more permissive
JoshMock File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can see the
onResponseClose()
is throwingResponse aborted while reading the body
, which is also emitted on anEPIPE
(shown below in line 255). These two messages should be distinct, since we won't know which one caused this message.It also appears we don't remove this listener. It seems like we should remove it in the same places we remove
data
andend
, most specifically ononEnd()
. I'm wondering if the listener is going off when the socket closes, making it seem like an otherwise successful call failed.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They're both
EPIPE
errors, which is why I gave them the same error message. It's the same symptom, just happening under slightly different circumstances: one gets a response body back, the other doesn't. That difference requires you to inspect the error'smeta
property to tell the difference, but I can use a slightly different message to help distinguish them further.While the 'close' event should be implicitly cleaned up during garbage collection, it won't hurt to explicitly remove those listeners at the end of the lifecycle.
I've made both of these changes in #266. Please take a look!