-
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: emit 'pause' on unpipe #32476
Conversation
unpipe should use pause() instead of mutating state.flowing directly so that pausing side effects such as emitting 'pause' are properly performed. Fixes: nodejs#32470
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.
I think this might also fix #32291?
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
Should we fast track this and get it included in v13.12.0? I don't know if it should so this should not count as 1 of the 2 +1s |
This doesn't have green CI yet. Maybe flaky test (test.parallel/test-tls-root-certificates)? I'll do a rerun/resume once it's complete (osx always takes time). I seem to be encountering quite a lot of flakiness nowadays. |
|
@MylesBorins Does that mean I can land this on master without green CI or should I keep trying until green CI is achieved? |
@ronag kicked off CI again. We should try and get green CI |
We did it!!! Landed in 0d0f151 |
unpipe should use pause() instead of mutating
state.flowing directly so that pausing side
effects such as emitting 'pause' are properly
performed.
Fixes: #32470
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes