-
Notifications
You must be signed in to change notification settings - Fork 30k
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
test: deflake test-http-many-ended-pipelines #38018
Conversation
client.on('error', function(err) { | ||
// The socket might be destroyed by the other peer while data is still | ||
// being written. | ||
assert.strictEqual(err.code, 'ECONNRESET'); |
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 think err.code
can also be 'EPIPE'
or 'ECONNABORTED'
but I was not able to reproduce. Should we handle that in advance or do it if/when it will occur?
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'd say let's do it when it occurs.
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.
Perhaps you can add a comment right now that says "EPIPE might be valid too but we haven't seen it yet" or something like that?
The socket might be destroyed by the other peer while data is still being written. Add the missing error handler. Fixes: nodejs#37291
Landed in cc4ee6c. |
The socket might be destroyed by the other peer while data is still
being written. Add the missing error handler.
Fixes: #37291