Skip to content

stream: destroy fixes - #29058

Closed
ronag wants to merge 2 commits into
nodejs:masterfrom
nxtedition:stream-no-error-after-error
Closed

ronag wants to merge 2 commits into
nodejs:masterfrom
nxtedition:stream-no-error-after-error

Conversation

@ronag

@ronag ronag commented Aug 8, 2019 •

Copy link
Copy Markdown
Member

Only emit error once.

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

NOTE TO SELF: After merge, look into emit in nextTick. Look into prefinish & nextTick.

@nodejs-github-bot nodejs-github-bot added the stream Issues and PRs related to Node.js streams. label Aug 8, 2019
@ronag
ronag force-pushed the stream-no-error-after-error branch 18 times, most recently from d6cc7ba to f82b56a Compare August 9, 2019 07:56
@ronag ronag mentioned this pull request Aug 9, 2019
3 of 4 tasks
@ronag ronag changed the title stream: error once stream: destroy fixes Aug 9, 2019
@ronag ronag mentioned this pull request Aug 9, 2019
2 tasks done
@ronag

ghost commented Aug 9, 2019 •

Copy link
Copy Markdown
Member Author

@mcollina: I tried combining some PR's into commits in one PR to ease review. I think this is how you prefer it?

@ronag
ronag force-pushed the stream-no-error-after-error branch 7 times, most recently from c0bb972 to 8e1883c Compare August 9, 2019 15:59
Comment thread doc/api/stream.md Resolved
@nodejs-github-bot

ghost commented Aug 15, 2019

Copy link
Copy Markdown
Collaborator

@Trott

ghost commented Aug 15, 2019

Copy link
Copy Markdown
Member

@Trott

ghost commented Aug 15, 2019

Copy link
Copy Markdown
Member

@mcollina OK to remove tsc-agenda since it now has three TSC approvals?

@nodejs-github-bot

ghost commented Aug 16, 2019

Copy link
Copy Markdown
Collaborator

@nodejs-github-bot

ghost commented Aug 16, 2019

Copy link
Copy Markdown
Collaborator

@nodejs-github-bot

ghost commented Aug 16, 2019

Copy link
Copy Markdown
Collaborator

@mcollina mcollina removed the tsc-agenda Issues and PRs to discuss during Technical Steering Committee meetings. label Aug 16, 2019
@mcollina

ghost commented Aug 16, 2019

Copy link
Copy Markdown
Member

@Trott removed

@ronag
ronag force-pushed the stream-no-error-after-error branch from 8558a3c to b432d4d Compare August 16, 2019 09:07
@ronag

ghost commented Aug 16, 2019

Copy link
Copy Markdown
Member Author

That force push was a mistake and has been reverted.

@ronag
ronag force-pushed the stream-no-error-after-error branch from b432d4d to 5c1fb91 Compare August 16, 2019 11:02
@ronag

ghost commented Aug 16, 2019

Copy link
Copy Markdown
Member Author

Fixed @Trott doc nit.

@ronag
ronag force-pushed the stream-no-error-after-error branch from 5c1fb91 to 2d36120 Compare August 16, 2019 11:03
@ronag
ronag force-pushed the stream-no-error-after-error branch from 2d36120 to dcec025 Compare August 16, 2019 11:03
@nodejs-github-bot

ghost commented Aug 17, 2019

Copy link
Copy Markdown
Collaborator

@Trott

ghost commented Aug 17, 2019

Copy link
Copy Markdown
Member

Landed in 4a2bd69

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

semver-major PRs that contain breaking changes and should be released in the next major version. stream Issues and PRs related to Node.js streams.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants