-
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
[v13.x backport] stream: support passing generator functions into pipeline() #31975
[v13.x backport] stream: support passing generator functions into pipeline() #31975
Conversation
Since this backport contains multiple commits I'm unsure where to add the |
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.
Backport-PR-URL: nodejs#31975 PR-URL: nodejs#31223 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Anna Henningsen <[email protected]>
If the destination was an async function any error thrown from that function would be swallowed. Backport-PR-URL: nodejs#31975 PR-URL: nodejs#31835 Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Denys Otrishko <[email protected]>
There was an edge case where an incorrect assumption was made in regardos whether eos/finished means that the stream is actually destroyed or not. Backport-PR-URL: nodejs#31975 PR-URL: nodejs#31940 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
995dcc6
to
23011b9
Compare
Added Backport-PR-URL to each commit |
@ronag each commit also needs the normal (update, nevermind - this looks like a bug in ncu landing behavior!) |
@nodejs/releasers would someone else be willing to review this? with only 1 approval the required waiting period is 97 more hours and I'd like to finish preparing the release unless this can be left off it. It does, however, block clean landing of ~10 other streams backports. |
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.
A little bit rubber-stampy of me but this looks good to me.
Backport-PR-URL: #31975 PR-URL: #31223 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Anna Henningsen <[email protected]>
If the destination was an async function any error thrown from that function would be swallowed. Backport-PR-URL: #31975 PR-URL: #31835 Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Denys Otrishko <[email protected]>
There was an edge case where an incorrect assumption was made in regardos whether eos/finished means that the stream is actually destroyed or not. Backport-PR-URL: #31975 PR-URL: #31940 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
Landed in 8ad64b8...8a2b62e |
#31223
Also includes some required follow up fixes.
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes