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

process: remove protection for SyncWriteStream destroy in stdio #26902

Closed
wants to merge 1 commit into from

Conversation

mcollina
Copy link
Member

#26691 introduced an if to protect
against SyncWriteStream not using the default .destroy() mechanism.
This change removes that as SyncWriteStream now use standard .destroy().

See: #26691

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • commit message follows commit guidelines

nodejs#26691 introduced an if to protect
against SyncWriteStream not using the default .destroy() mechanism.
This change removes that as SyncWriteStream now use standard .destroy().

See: nodejs#26691
@nodejs-github-bot nodejs-github-bot added the process Issues and PRs related to the process subsystem. label Mar 25, 2019
@mcollina
Copy link
Member Author

@BridgeAR BridgeAR added dont-land-on-v6.x author ready PRs that have at least one approval, no pending requests for changes, and a CI started. labels Mar 25, 2019
@mcollina
Copy link
Member Author

Landed in d4eda4d

@mcollina mcollina closed this Mar 28, 2019
@mcollina mcollina deleted the remove-if-stdio branch March 28, 2019 12:54
mcollina added a commit that referenced this pull request Mar 28, 2019
#26691 introduced an if to protect
against SyncWriteStream not using the default .destroy() mechanism.
This change removes that as SyncWriteStream now use standard .destroy().

See: #26691

PR-URL: #26902
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: Ruben Bridgewater <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Anna Henningsen <[email protected]>
BethGriggs pushed a commit that referenced this pull request Apr 5, 2019
#26691 introduced an if to protect
against SyncWriteStream not using the default .destroy() mechanism.
This change removes that as SyncWriteStream now use standard .destroy().

See: #26691

PR-URL: #26902
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: Ruben Bridgewater <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Anna Henningsen <[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. process Issues and PRs related to the process subsystem.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants