Skip to content

stream: enable autoDestroy by default - #30623

Closed
ronag wants to merge 8 commits into
nodejs:masterfrom
nxtedition:stream-auto-destroy
Closed

stream: enable autoDestroy by default#30623
ronag wants to merge 8 commits into
nodejs:masterfrom
nxtedition:stream-auto-destroy

Conversation

@ronag

@ronagronag commented Nov 24, 2019

Copy link
Copy Markdown
Member

Enable autoDestroy by default.

semver-major

Refs: #30621

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-botnodejs-github-bot added the lib / src Issues and PRs related to general changes in the lib or src directory. label Nov 24, 2019
@ronag

Copy link
Copy Markdown
MemberAuthor

This will need CITGM

@mcollina

Copy link
Copy Markdown
Member

Can you open up a tracking issues with all the node core implementations that would need to be updated to autoDestroy: true?

@ronag

ronag commented Nov 24, 2019

Copy link
Copy Markdown
MemberAuthor

Can you open up a tracking issues with all the node core implementations that would need to be updated to autoDestroy: true?

I think you mean autoDestroy: false? I've already updated them in this PR. Or am I missing/misunderstanding something?

@mcollina

Copy link
Copy Markdown
Member

I think we should migrate all of those you have set to false in this PR to true before node v14 is cut.

@ronag

ronag commented Nov 24, 2019

Copy link
Copy Markdown
MemberAuthor

I think we should migrate all of those you have set to false in this PR to true before node v14 is cut.

#30625

Though realistically I don't think we will be able to do this for internal/http2/core.js.

Just to clarify. Are you proposing we do not merge this PR until we've migrated?

@mcollina

Copy link
Copy Markdown
Member

I’m fine with landing this before that happens.

@lpincalpinca added the semver-major PRs that contain breaking changes and should be released in the next major version. label Nov 24, 2019
@ronagronag mentioned this pull request Nov 24, 2019
6 tasks
@ronag

ronag commented Dec 1, 2019

Copy link
Copy Markdown
MemberAuthor

@Trott: I think this needs a CITGM?

@mcollina: Do you think you can approve this PR or is there something further that needs to be addressed?

@mcollinamcollina left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

lgtm

@mcollina

Copy link
Copy Markdown
Member

cc @nodejs/tsc this needs a review.

@Trott

Trott commented Dec 2, 2019

Copy link
Copy Markdown
Member

@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@BridgeAR

Copy link
Copy Markdown
Member

@nodejs/tsc this has three LGs but it needs one more LG from the TSC. PTAL

@BridgeAR

Copy link
Copy Markdown
Member

Seems like this has failing test cases.

@ronag

Copy link
Copy Markdown
MemberAuthor

Seems like this has failing test cases.

Not sure how to resolve those. I'm running on OSX and I can't reproduce the OSX failures. Are we sure the CI is correct?

@BridgeAR

Copy link
Copy Markdown
Member

@ronag these two tests fail (even on OSX):

  • test/parallel/test-stream-catch-rejections.js
  • test/parallel/test-stream-writable-write-cb-twice.js

You can click on the failed results here and you should get an overview of Jenkins with the specific Job that was run. E.g., https://ci.nodejs.org/job/node-test-commit-osx/nodes=osx1011/30941/.

You can click on the specific part of the job and see e.g., the failure output:
https://ci.nodejs.org/job/node-test-commit-osx/nodes=osx1011/30941/testReport/junit/(root)/test/parallel_test_stream_catch_rejections/
https://ci.nodejs.org/job/node-test-commit-osx/nodes=osx1011/30941/testReport/junit/(root)/test/parallel_test_stream_writable_write_cb_twice/

@ronag

Copy link
Copy Markdown
MemberAuthor

@BridgeAR: Something is wrong here test-stream-catch-rejections doesn't even exist. Did this CI run against a different branch/PR?

@ronag

Copy link
Copy Markdown
MemberAuthor

Ah, it does a merge against master. I'll rebase this and re-run tests.

@ronag
ronagforce-pushed the stream-auto-destroy branch 2 times, most recently from 052da2a to c3fda6bCompareDecember 25, 2019 20:04
@ronag

Copy link
Copy Markdown
MemberAuthor

@BridgeAR: another CI please

Comment threadlib/_stream_readable.js Outdated
@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@ronag
ronagforce-pushed the stream-auto-destroy branch from 6327773 to 58424eeCompareDecember 26, 2019 19:23
@ronag

Copy link
Copy Markdown
MemberAuthor

rebased

@TrottTrott added the notable-change PRs with changes that should be highlighted in changelogs. label Dec 27, 2019
@ronagronag mentioned this pull request Dec 29, 2019
4 tasks
@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@ronag
ronagforce-pushed the stream-auto-destroy branch from 58424ee to 616c56eCompareJanuary 1, 2020 12:10
@ronag

ronag commented Jan 1, 2020

Copy link
Copy Markdown
MemberAuthor

rebased to fix conflicts

@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

Comment threadtest/parallel/test-stream-writable-write-cb-twice.js Outdated
Comment threadtest/parallel/test-stream-writable-write-cb-twice.js Outdated
Comment threadtest/parallel/test-stream-writable-write-cb-twice.js Outdated
Comment threadtest/parallel/test-stream-writable-write-cb-twice.js Outdated
@nodejs-github-bot

This comment has been minimized.

@nodejs-github-bot

This comment has been minimized.

@nodejs-github-bot

nodejs-github-bot commented Jan 2, 2020

Copy link
Copy Markdown
Collaborator

BridgeAR pushed a commit that referenced this pull request Jan 3, 2020
PR-URL: #30623
Refs: #30621
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Rich Trott <rtrott@gmail.com>
@BridgeAR

Copy link
Copy Markdown
Member

Landed in 4bec6d1 🎉

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

Labels

author readyPRs that have at least one approval, no pending requests for changes, and a CI started.lib / srcIssues and PRs related to general changes in the lib or src directory.notable-changePRs with changes that should be highlighted in changelogs.semver-majorPRs that contain breaking changes and should be released in the next major version.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants

@ronag@mcollina@Trott@nodejs-github-bot@BridgeAR@lpinca