-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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: fix finished w/ 'close' before 'end' #31545
Conversation
Since there was problems with a similar PR before I would suggest a semver-major on this one. |
37c83e4
to
7626cf9
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
CITGM failure on socket.io might be worth looking into. |
rebased to fix conflict |
7626cf9
to
770186b
Compare
Looked into socket.io and winston CITGM failures. Was not able to find anything strange on MacOS. |
a1d6950
to
88c260e
Compare
CITGM failures worth looking into:
I'm pretty much stuck on these. Unable to reproduce. |
CI passes, not sure if author-ready label should be applied given CITGM status. Please remove if appropriate. |
@nodejs/streams @nodejs/tsc This seems OK to me as a semver-major, but could use more reviews. CI and CITGM both look good. |
This needs a rebase, sorry |
88c260e
to
9649e26
Compare
rebased |
9649e26
to
e6fb01c
Compare
@addaleax: rebased, approve? |
rebased to fix conflicts |
e6fb01c
to
b470fa0
Compare
rebased to fix conflicts |
07c6efd
to
6a90b56
Compare
Emitting 'close' before 'end' on a Readable should result in a premature close error.
6a90b56
to
f1cf385
Compare
This has 2 TSC approvals but I believe @Trott's approval is conditioned on further review from @nodejs/streams and/or @nodejs/tsc. |
You can treat mine the same as any other approval. How about we wait another 72 hours in a last effort to get a few more eyes on this? @nodejs/collaborators |
Landed in 7cafd5f |
Emitting 'close' before 'end' on a Readable should result in a premature close error. PR-URL: #31545 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Rich Trott <[email protected]>
Emitting 'close' before 'end' on a Readable should result in a premature close error.
This is related to the one that caused trouble in #29699. Includes the fix proposed in #29724.
Related discussion: https://github.com/nodejs/node/pull/29724/files#r329128356
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes