-
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
Stream.pipeline does not re-emit errors without callback #20303
Labels
stream
Issues and PRs related to the stream subsystem.
Comments
addaleax
changed the title
Stream.pipeline shipped with a huge bug?
Stream.pipeline does not re-emit errors without callback
Apr 25, 2018
You already seem to have a PR for this, would you be willing to port that? |
Yeah, I can try. I might have some time later today. |
@addaleax working on a PR now but it seems that I can't run the test suite without xcode 😞 |
@phated If it would be easier for you if somebody else took this over at some point, I think that wouldn’t be an issue either |
4 tasks
phated
added a commit
to phated/node
that referenced
this issue
May 30, 2018
Fixes an issue where Stream.pipeline wouldn't re-throw errors on a stream if no callback was specified, thus swallowing said errors. Fixes: nodejs#20303
addaleax
pushed a commit
that referenced
this issue
May 31, 2018
Fixes an issue where Stream.pipeline wouldn't re-throw errors on a stream if no callback was specified, thus swallowing said errors. Fixes: #20303 PR-URL: #20437 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Node 10
Stream.pipeline
doesn't re-emit errors when no callback is given. I opened this issue (mafintosh/pump#32) onpump
before it was ported here but it was ignored.The text was updated successfully, but these errors were encountered: