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

fs: fix missing 'error' event in ReadStream/WriteSteam destroy(err) #19735

Closed
wants to merge 2 commits into from

Conversation

range3
Copy link
Contributor

@range3 range3 commented Apr 1, 2018

fs.ReadStream / fs.WriteStrem destroy([error]) function
should emit 'error' event if [error] is set.

Fixes: #19727

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

@nodejs-github-bot nodejs-github-bot added the fs Issues and PRs related to the fs subsystem / file system. label Apr 1, 2018
@@ -0,0 +1,41 @@
// Copyright Joyent, Inc. and other Node contributors.
Copy link
Contributor

@mscdex mscdex Apr 1, 2018

Choose a reason for hiding this comment

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

IIRC all of this commented text shouldn't be added for new tests.

Copy link
Member

Choose a reason for hiding this comment

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

Yeah, new source files should never include the copyright boilerplate

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I removed the copyright boilerplate. thanks!

range3 added 2 commits April 2, 2018 08:54
fs.ReadStream / fs.WriteStrem destroy([error]) function
should emit 'error' event if [error] is set.

Fixes: nodejs#19727
@lpinca lpinca added the stream Issues and PRs related to the stream subsystem. label Apr 2, 2018
@lpinca
Copy link
Member

lpinca commented Apr 2, 2018

@BridgeAR BridgeAR added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Apr 9, 2018
@trivikr
Copy link
Member

trivikr commented Apr 9, 2018

@BridgeAR
Copy link
Member

BridgeAR commented Apr 9, 2018

Landed in 6e2d5af 🎉

@BridgeAR BridgeAR closed this Apr 9, 2018
BridgeAR pushed a commit to BridgeAR/node that referenced this pull request Apr 9, 2018
fs.ReadStream / fs.WriteStream destroy([error]) function
should emit 'error' event if `error` is set.

PR-URL: nodejs#19735
Fixes: nodejs#19727
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Trivikram Kamat <[email protected]>
Reviewed-By: Ruben Bridgewater <[email protected]>
@BridgeAR
Copy link
Member

BridgeAR commented Apr 9, 2018

@range3 congratulations on your first commit to Node.js and to officially becoming a contributor!

targos pushed a commit that referenced this pull request Apr 12, 2018
fs.ReadStream / fs.WriteStream destroy([error]) function
should emit 'error' event if `error` is set.

PR-URL: #19735
Fixes: #19727
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Trivikram Kamat <[email protected]>
Reviewed-By: Ruben Bridgewater <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
author ready PRs that have at least one approval, no pending requests for changes, and a CI started. fs Issues and PRs related to the fs subsystem / file system. stream Issues and PRs related to the stream subsystem.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

fs.ReadStream / fs.WriteStream destroy(err) function doesn't emit error event
8 participants