Skip to content

Conversation

@targos
Copy link
Member

@targos targos commented Mar 4, 2018

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

@targos targos added wip Issues and PRs that are still a work in progress. semver-major PRs that contain breaking changes and should be released in the next major version. errors Issues and PRs related to JavaScript errors originated in Node.js core. labels Mar 4, 2018
@nodejs-github-bot nodejs-github-bot added the lib / src Issues and PRs related to general changes in the lib or src directory. label Mar 4, 2018
@targos targos force-pushed the port-internal-errors branch 3 times, most recently from 04b55eb to 8280260 Compare March 6, 2018 09:37
@targos targos removed the wip Issues and PRs that are still a work in progress. label Mar 6, 2018
@targos
Copy link
Member Author

targos commented Mar 6, 2018

Copy link
Member

@BridgeAR BridgeAR left a comment

Choose a reason for hiding this comment

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

LGTM with my comment addressed.

Copy link
Member

Choose a reason for hiding this comment

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

Seems like I made a mistake here. I think this should stay as Error.

Copy link
Member Author

Choose a reason for hiding this comment

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

You are right. I fixed it.

@targos targos force-pushed the port-internal-errors branch from 8280260 to 7346190 Compare March 6, 2018 14:30
@BridgeAR
Copy link
Member

BridgeAR commented Mar 6, 2018

If all errors got ported to the new system makeNodeError should be obsolete (it is still used in the SystemError' class but that could be switched to makeNodeErrorWithCode` instead).

@targos
Copy link
Member Author

targos commented Mar 6, 2018

@BridgeAR yes, I'm working on a follow-up PR to remove dead code from internal/errors

@joyeecheung
Copy link
Member

@BridgeAR
Copy link
Member

BridgeAR commented Mar 6, 2018

@targos seems like a require statement is missing.

@targos targos force-pushed the port-internal-errors branch from 7346190 to 73c3b0a Compare March 7, 2018 10:12
@targos
Copy link
Member Author

targos commented Mar 7, 2018

Fixed. It was a new error that came with the rebase.
CI: https://ci.nodejs.org/job/node-test-pull-request/13563/

Edit: Windows rebuild: https://ci.nodejs.org/job/node-test-commit-windows-fanned/16238/

targos added a commit that referenced this pull request Mar 7, 2018
PR-URL: #19137
Reviewed-By: Anatoli Papirovski <[email protected]>
Reviewed-By: Ruben Bridgewater <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Joyee Cheung <[email protected]>
@targos
Copy link
Member Author

targos commented Mar 7, 2018

Landed in 1d2fd8b

@targos targos closed this Mar 7, 2018
MayaLekova pushed a commit to MayaLekova/node that referenced this pull request May 8, 2018
PR-URL: nodejs#19137
Reviewed-By: Anatoli Papirovski <[email protected]>
Reviewed-By: Ruben Bridgewater <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Joyee Cheung <[email protected]>
@targos targos deleted the port-internal-errors branch October 17, 2020 12:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

errors Issues and PRs related to JavaScript errors originated in Node.js core. lib / src Issues and PRs related to general changes in the lib or src directory. semver-major PRs 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