-
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: fix .end() error propagation #36817
Conversation
96a3e8f
to
db00cc2
Compare
@nodejs/stream |
e25f804
to
48ea4c2
Compare
c8eb497
to
5443a22
Compare
@lpinca: Though I agree that the behavior is a little strange and should be discussed I'm not sure it's relevant for this PR other than we noticed it with the tests added here. |
I agree, I vaguely remember having already discussed it in an old PR (It was probably the PR calling all pending callbacks on error) but I may be wrong. |
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.
RSLGMT
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.
lgtm
PR-URL: #36817 Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
Landed in a4fce32 |
PR-URL: #36817 Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
mark this as semver-major post-release as it broke things in v15 :(, see #37027 for more details. cc @nodejs/tsc |
No description provided.