| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
@nodejs/ctc ... can I please get a review on this? |
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
There was a problem hiding this comment.
almost there
Sorry, something went wrong.
There was a problem hiding this comment.
missing space
Sorry, something went wrong.
There was a problem hiding this comment.
nit: passed in?
Sorry, something went wrong.
There was a problem hiding this comment.
nit: communication
Sorry, something went wrong.
There was a problem hiding this comment.
maybe ERR_IPC_CHANNEL_CLOSED?
Sorry, something went wrong.
There was a problem hiding this comment.
ditto. ERR_IPC_INVALID_HANDLE_TYPE
Sorry, something went wrong.
There was a problem hiding this comment.
If I read it correctly, this would print The "options" argument must be type Object. It looks better to me as The "options" argument must be of type Object
Sorry, something went wrong.
There was a problem hiding this comment.
It would be nice to have some tests for this function OK, tests are in #11294
Sorry, something went wrong.
There was a problem hiding this comment.
The name argument is missing
Sorry, something went wrong.
There was a problem hiding this comment.
ditto
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
There was a problem hiding this comment.
Why did you remove this check? (The test for it is removed in the second commit btw)
Sorry, something went wrong.
There was a problem hiding this comment.
Because of issues in the loading order of the errors.js module relative to assert.js on startup. There is a circular dependency that happens that causes the util.js used within assert.js to fail depending on when assert is loaded. I could replace this with a simple throw rather than the call to assert if you'd be more comfortable with that.
Sorry, something went wrong.
There was a problem hiding this comment.
I'm fine with removing it. I was just curious. The risk of reusing the same code is low if we keep them together and in alphabetical order.
Sorry, something went wrong.
There was a problem hiding this comment.
unnecessary new line
Sorry, something went wrong.
There was a problem hiding this comment.
whoops! fixed
Sorry, something went wrong.
There was a problem hiding this comment.
please keep the codes in alphabetical order relative to the existing ones.
Sorry, something went wrong.
There was a problem hiding this comment.
please bundle this change with the same commit that removed the error
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM. This needs a rebase.
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
|
Thank you @mhdawson and @targos. Rebased again and new CI before landing: https://ci.nodejs.org/job/node-test-pull-request/7715/ |
Sorry, something went wrong.
Use of assert must be lazy to allow errors to be used early before the process is completely set up
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Ref: #11273
Semver-major because error messages are changed.
Checklist
Affected core subsystem(s)
errors, child_process