Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
fix --inspect and its ilk; closes #3681 #3699
fix --inspect and its ilk; closes #3681 #3699
Changes from all commits
0f6b91d
2abc1a8
9b4c6f0
79b5f09
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just noted, there is a Mocha flag
-r
and also one innodeEnv
. In this case flag is put into mocha bucket. Could lead to conflicts?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mocha's
--require
and-r
are both preferred over Node's, seeisNodeFlag
inlib/cli/node-flags.js
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
down L131:
when Node env variable NODE_OPTIONS is used, it just feeds the CL arguments list, I guess. Does the child process inherit these variables correctly?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the short answer is "yes". the longer answer is we ignore
NODE_OPTIONS
, and whatever's there does not go into any arguments list. when node args andNODE_OPTIONS
conflict, node does whatever node does to resolve it.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(sic)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we save ALL found node args here so we can use them in the boolean array below.
the values are saved as whatever they are; if there is no value (e.g.,
--inspect
), then the value is saved astrue
, which is what yargs-unparser understands.Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This one is failing with "Uncaught UnexpectedError" on my Windows. I need to investigate further.
The other three "Node.js v8+" tests do pass.
"Node.js v6" tests are skipped.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, I don't know how to fix this. that's where I was hoping you could help (eventually)
killing the subprocess using our method (because
inspect-brk
means you're in a debugging session) doesn't return any process output nor an exit code on windows. the method is likely wrong for windows (usingSIGINT
on posix), but I don't know what the correct one is.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
change to:
This way the
err.code
is 1 (not undefined which crashesto have failed
).A timeout of 1000 is too short,
res
may not be ready, yet =>to contain output
fails.On my windows platform the four 'Node.js v8+' tests do pass.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't quite understand what you're asking for