| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
This has a dependency on #34103 which I had to include. |
Sorry, something went wrong.
|
@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. |
Sorry, something went wrong.
Sorry, something went wrong.
|
Weird test failure? AssertionError [ERR_ASSERTION]: benchmark file not running exactly one configuration in test:? |
Sorry, something went wrong.
There was a problem hiding this comment.
lgtm - I think this is the right thing to do long term.
Sorry, something went wrong.
|
@nodejs/streams |
Sorry, something went wrong.
Sorry, something went wrong.
We're still seeing this in the CI on multiple platforms. Anyone able to take a look please? |
Sorry, something went wrong.
Who can help with that? I have no clue. |
Sorry, something went wrong.
|
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. |
Sorry, something went wrong.
@ronag I think you have to force a single configuration for your benchmark test in the test/benchmark/test-benchmark-streams.js This is not the case since #31755. |
Sorry, something went wrong.
Sorry, something went wrong.
Fixes some compatibility issues where it is expected that for await stops reading when the stream is destroyed. Refs: nodejs#34887
|
This needs some more collaborator review to ensure we are confident with landing it in 14.x. |
Sorry, something went wrong.
|
Just FYI in case it shows up in this PR, it looks like test-asan is failing on v14.x, i'm trying to figure that out in #35641. |
Sorry, something went wrong.
|
@BethGriggs Green CI. Just needs another approval or two. Thanks for the ping! |
Sorry, something went wrong.
|
What are the commits that are backported here? Have we got a references to those two PRs? |
Sorry, something went wrong.
|
Yea I seem to have ruined the commit msg. The backported PR's are: Also relevant: |
Sorry, something went wrong.
|
@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. |
Sorry, something went wrong.
There was a problem hiding this comment.
lgtm
Sorry, something went wrong.
|
what is the diff vs what we have on master? |
Sorry, something went wrong.
Once #35640 is merged, I believe they are exactly the same. |
Sorry, something went wrong.
|
@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? |
Sorry, something went wrong.
|
I think we would like to have this in v14 to simplify backporting. |
Sorry, something went wrong.
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.) |
Sorry, something went wrong.
|
@ronag would you be able to rebase so we can make sure the asan test isn't broken by this PR |
Sorry, something went wrong.
|
@nodejs/streams we still need 1 more sign off on this |
Sorry, something went wrong.
|
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 |
Sorry, something went wrong.
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 <rtrott@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
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 <luigipinca@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
|
Landed in 573410f Hopefully I captures things accurately in the commit message |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
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
Writable stream could emit 'finish' after 'close'.
PR-URL: #32933
Reviewed-By: Luigi Pinca luigipinca@gmail.com
Reviewed-By: Matteo Collina matteo.collina@gmail.com