-
Notifications
You must be signed in to change notification settings - Fork 30.3k
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: drain Transform with 0 highWaterMark #40947
Conversation
385da26
to
cac9496
Compare
cac9496
to
a4453b0
Compare
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
@nodejs/streams |
This comment has been minimized.
This comment has been minimized.
Co-authored-by: Luigi Pinca <luigipinca@gmail.com>
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Landed in 37f1dd9 |
This fix is faulty and causes a regression in my stream code, which can no longer use the I explicitly test against this here, since my transform stream relies on it working. I guess I will have to continue running node 14 on my servers. |
@kanongil can you please open a new separate issue (pointing to this PR) and I'll ping stream maintainers? |
@benjamingr It's already described in #42457, which I have amended with my info. |
Fixes: nodejs#40935 Refs: nodejs#40947 Refs: nodejs#42457
Fixes: nodejs#40935 Refs: nodejs#40947 Refs: nodejs#42457
Fixes: #40935