-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
EPIPE errors from aborted request #4296
Comments
Thanks for the report! Very timely— if you're interested you can check-out progress on a similar (or potentially the same?) issue in #4295. |
Hmm, we already test for errors during stream transmission, but not combined with a client abort. Guess we need another test case. |
Actually, this does not make sense. The Response will have the Once it calls This means that it should never even try to write. Unless maybe you have set the hidden |
maybe related? nodejs/node#40553 can you try node 14.17 instead of node 14.18? |
Hi Folks! I'm upgrade my app to node 14 and
this happen using node V14.18.1 orV14.15.5 |
@aaestrada If you can reliably reproduce the issue, please file an issue. |
Regardless of what triggers this, hapi should probably handle thrown errors when calling |
Support plan
Context
What are you trying to achieve or the steps to reproduce?
Our Sentry setup has caught and logged the following error several times:
This apparently happens when the client aborts its request; it's preceded by
["request","error","abort"]
and["response","error","aborted"]
error messages.We've gotten several errors like this, although I haven't yet tried to reproduce it locally or on demand.
What was the result you got?
An EPIPE error from an apparently uncaught exception.
What result did you expect?
No additional errors logged other than the abort message.
The text was updated successfully, but these errors were encountered: