Skip to content
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

Closed
wants to merge 6 commits into from

Conversation

ronag
Copy link
Member

@ronag ronag commented Apr 19, 2020

Writable stream could emit 'finish' after 'close'.

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • documentation is changed or added
  • commit message follows commit guidelines

@ronag ronag added the stream Issues and PRs related to the stream subsystem. label Apr 19, 2020
@ronag ronag force-pushed the stream-finish-after-close branch 3 times, most recently from 8bf2442 to ec3e537 Compare April 19, 2020 21:57
@ronag
Copy link
Member Author

ronag commented Apr 22, 2020

@nodejs/streams

Copy link
Member

@mcollina mcollina left a 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.

test/parallel/test-stream-writable-finish-destroyed.js Outdated Show resolved Hide resolved
test/parallel/test-stream-writable-finish-destroyed.js Outdated Show resolved Hide resolved
@ronag ronag force-pushed the stream-finish-after-close branch from f9154ec to 604191b Compare April 25, 2020 17:35
@ronag
Copy link
Member Author

ronag commented Apr 25, 2020

added some missing mustCalls

@ronag ronag force-pushed the stream-finish-after-close branch from 604191b to 7da4656 Compare April 25, 2020 17:37
@nodejs-github-bot
Copy link
Collaborator

@nodejs-github-bot
Copy link
Collaborator

lib/_stream_readable.js Outdated Show resolved Hide resolved
@ronag ronag force-pushed the stream-finish-after-close branch from 065eb38 to 706e189 Compare April 26, 2020 09:09
@ronag ronag requested a review from mcollina April 26, 2020 21:56
Copy link
Member

@mcollina mcollina left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@nodejs-github-bot
Copy link
Collaborator

ronag added a commit that referenced this pull request Apr 27, 2020
Writable stream could emit 'finish' after 'close'.

PR-URL: #32933
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Matteo Collina <[email protected]>
@ronag
Copy link
Member Author

ronag commented Apr 27, 2020

Landed in f5c11a1

@ronag ronag closed this Apr 27, 2020
BethGriggs pushed a commit that referenced this pull request Apr 27, 2020
Writable stream could emit 'finish' after 'close'.

PR-URL: #32933
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Matteo Collina <[email protected]>
@BethGriggs BethGriggs mentioned this pull request Apr 27, 2020
BethGriggs pushed a commit that referenced this pull request Apr 28, 2020
Writable stream could emit 'finish' after 'close'.

PR-URL: #32933
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Matteo Collina <[email protected]>
@ronag
Copy link
Member Author

ronag commented Apr 28, 2020

@targos
Copy link
Member

targos commented May 16, 2021

It seems #34887 should unblock this backport. @ronag would you still like it to happen?

@ronag
Copy link
Member Author

ronag commented May 16, 2021

Yes. I'm a little overloaded at the moment though. If you need help ping me again in a. week :).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stream Issues and PRs related to the stream subsystem.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants