-
-
Notifications
You must be signed in to change notification settings - Fork 31.5k
Stream.pipeline does not re-emit errors without callback #20303
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Labels
stream
Issues and PRs related to the stream subsystem.
Comments
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
# for free
to join this conversation on GitHub.
Already have an account?
# 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: