Skip to content

Handle EPIPE errors along with the current ECONNRESET #3443

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

Conversation

matthewsanders
Copy link

@matthewsanders matthewsanders commented Feb 1, 2017

There is an open issue with Node.js throwing EPIPE errors when you pipe to a closed stream. This was causing me unpredictable errors while loading pages.

The errors are pretty similar to ECONNRESET in the sense that you could simply try again and shouldn't throw every time it happens.

More info here: nodejs/node#947

There is an open issue with Node.js throwing EPIPE errors when you pipe to a closed stream.  This was causing me unpredictable errors while loading pages.

The errors are pretty similar to ECONNRESET in the sense that you could simply try again and shouldn't throw every time it happens.

More info here: nodejs/node#947
@wluu
Copy link

wluu commented Aug 2, 2017

I've been running into this issue with Protractor: angular/protractor#4294

After manually adding that fix, I have not seen the EPIPE errors in our test suites. Granted, I've been running our test suites with the fix only a couple of times so far.

@p0deje p0deje added C-nodejs JavaScript Bindings Z-awaiting review Archived: use GitHub review assignments labels Aug 3, 2017
@jleyba
Copy link
Contributor

jleyba commented Jan 16, 2018

Sorry we let this PR sit for a year without review :(

Retries for EPIPE errors was added in c41f9ef

@jleyba jleyba closed this Jan 16, 2018
@jleyba jleyba removed the Z-awaiting review Archived: use GitHub review assignments label Jan 16, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-nodejs JavaScript Bindings
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants