Uh oh!
There was an error while loading. Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork 34.2k
[v14.x backport] stream: simpler and faster Readable async iterator #34887
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
Conversation
ronag commented Aug 23, 2020 • edited
Loading Uh oh!
There was an error while loading. Please reload this page.
edited
Uh oh!
There was an error while loading. Please reload this page.
91ba1df to 8fecd44Compare This comment has been minimized.
This comment has been minimized.
8fecd44 to 6c942b0Compareronag commented Aug 23, 2020 • edited
Loading Uh oh!
There was an error while loading. Please reload this page.
edited
Uh oh!
There was an error while loading. Please reload this page.
This has a dependency on #34103 which I had to include. |
ronag commented Aug 23, 2020
@MylesBorins There are two backports in this PR. Would I need to open separate PRs? The first commit doesn't make much sense to backport without the second one. |
nodejs-github-bot commented Aug 23, 2020
ronag commented Aug 23, 2020
Weird test failure? |
mcollina left a comment
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 - I think this is the right thing to do long term.
ronag commented Sep 1, 2020
@nodejs/streams |
nodejs-github-bot commented Sep 1, 2020
richardlau commented Sep 1, 2020
We're still seeing this in the CI on multiple platforms. Anyone able to take a look please? |
ronag commented Sep 3, 2020
Who can help with that? I have no clue. |
09369a0 to fb2111eComparemhdawson commented Sep 3, 2020
Discussed in TSC meeting today, no objections raised by TSC members that were there. Myles, sees Matteo chiming that it is a good thing so comfortable that it land given that stream subsystem team members are signing off once ci is green. Removing the agenda tag. |
lundibundi commented Sep 3, 2020 • edited
Loading Uh oh!
There was an error while loading. Please reload this page.
edited
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
nodejs-github-bot commented Oct 14, 2020
Fixes some compatibility issues where it is expected that for await stops reading when the stream is destroyed. Refs: nodejs#34887
ronag commented Oct 14, 2020
This needs some more collaborator review to ensure we are confident with landing it in 14.x. |
BethGriggs commented Oct 14, 2020
Just FYI in case it shows up in this PR, it looks like |
ronag commented Oct 14, 2020 • edited
Loading Uh oh!
There was an error while loading. Please reload this page.
edited
Uh oh!
There was an error while loading. Please reload this page.
@BethGriggs Green CI. Just needs another approval or two. Thanks for the ping! |
mcollina commented Oct 14, 2020
What are the commits that are backported here? Have we got a references to those two PRs? |
ronag commented Oct 14, 2020 • edited
Loading Uh oh!
There was an error while loading. Please reload this page.
edited
Uh oh!
There was an error while loading. Please reload this page.
MylesBorins commented Oct 14, 2020
@ronag it seems like multipel prs + commits have all merged into one here. I'm assuming that it will be a lot of work to split them up... so in lieu of that I think we could treat this as an entirely new change that avoids needing to backport the other change. That does mean we will need at least 2 signoff before landing this. |
mcollina left a comment
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
mcollina commented Oct 14, 2020
what is the diff vs what we have on master? |
ronag commented Oct 14, 2020 • edited
Loading Uh oh!
There was an error while loading. Please reload this page.
edited
Uh oh!
There was an error while loading. Please reload this page.
Once #35640 is merged, I believe they are exactly the same. |
MylesBorins commented Oct 14, 2020 • edited
Loading Uh oh!
There was an error while loading. Please reload this page.
edited
Uh oh!
There was an error while loading. Please reload this page.
@mcollina@ronag . Should we rush getting this into the next 14? it will be the last release before LTS, planned to go out tomorrow I'll be honest, considering these changes caused issues in the past I'm a bit nervous about including them just before flipping the LTS bit, but perhaps I am being too conservative. What do y'all think? |
mcollina commented Oct 14, 2020
I think we would like to have this in v14 to simplify backporting. |
BethGriggs commented Oct 15, 2020
FWIW, i'm somewhat leaning the opposite way, and feel that (for the same reasons) this change should land before v14.x is promoted to LTS. (Assuming that CITGM is happy.) |
MylesBorins commented Oct 15, 2020
@ronag would you be able to rebase so we can make sure the asan test isn't broken by this PR |
MylesBorins commented Oct 15, 2020
@nodejs/streams we still need 1 more sign off on this |
MylesBorins commented Oct 15, 2020
I'm 99% sure the test failure here was broken on 14.x before this was opened and the PR just needs a rebase. I'm going to land this as soon as #35640 lands |
Fixes some compatibility issues where it is expected that for await stops reading when the stream is destroyed. Refs: #34887 PR-URL: #35640 Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: James M Snell <[email protected]>
includes: * stream: simpler and faster Readable async iterator * stream: don't destroy on async iterator success * stream: async iterator stop read if destroyed PR-URL: #34887 Refs: #34035 Refs: #35122 Refs: #35640 Refs: #34680 Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
MylesBorins commented Oct 15, 2020 • edited
Loading Uh oh!
There was an error while loading. Please reload this page.
edited
Uh oh!
There was an error while loading. Please reload this page.
Landed in 573410f Hopefully I captures things accurately in the commit message |
A backport of semver-major labelled PR. Was discussed with TSC who gave a go ahead to open a PR and try to gain approval from collaborators.
PR: #34035
Refs: #34680
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passesWritable stream could emit 'finish' after 'close'.
PR-URL: #32933
Reviewed-By: Luigi Pinca [email protected]
Reviewed-By: Matteo Collina [email protected]