-
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: don't emit prefinish after error or close #39332
Conversation
@nodejs/streams |
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
This looks like a patch, but it could be breaking. I've added a labels so that it is not backported to v14 straight away. |
PR-URL: #39332 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: James M Snell <[email protected]>
Landed in 7a7ba82 |
PR-URL: #39332 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: James M Snell <[email protected]>
It doesn't land cleanly on v14.x-staging.
|
This change somehow breaks Apache Avro JS module [1] [2]. With Node.js 16 the
to the MessageDecoder (a Transformer) but none of them is triggered. The only way to "fix" the tests is to emit Do you have an idea what is going wrong ? |
No description provided.