-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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: don't emit finish after close #32933
Conversation
8bf2442
to
ec3e537
Compare
@nodejs/streams |
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.
Given that the PR mention 'close'
, it would be good to add a few mustCall()
/mustNotCall()
for that as well.
f9154ec
to
604191b
Compare
added some missing mustCalls |
Writable stream could emit 'finish' after 'close'.
604191b
to
7da4656
Compare
065eb38
to
706e189
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
Writable stream could emit 'finish' after 'close'. PR-URL: #32933 Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
Landed in f5c11a1 |
Writable stream could emit 'finish' after 'close'. PR-URL: #32933 Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
Writable stream could emit 'finish' after 'close'. PR-URL: #32933 Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
Yes. I'm a little overloaded at the moment though. If you need help ping me again in a. week :). |
Writable stream could emit 'finish' after 'close'.
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes