-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
inspector: listen on process.debugPort #8386
Conversation
LGTM if CI is green. |
@cjihrig this needs a rebase :) |
@addaleax rebased. Sorry for the delay. PTAL |
CI failures look unrelated. Since this is semver major, can another CTC member take a look? Perhaps @ofrobots? |
ping @nodejs/ctc, please. |
LGTM |
1 similar comment
LGTM |
This commit consolidates the debugging port used by the inspector and Node's legacy debugger. Fixes: nodejs#8201 PR-URL: nodejs#8386 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Fedor Indutny <fedor.indutny@gmail.com>
Final CI came back OK: https://ci.nodejs.org/job/node-test-pull-request/4040/ |
Sorry that I missed the ping on this. The use of different ports between inspector and the old debug protocol was quite intentional due to (very valid) concerns raised by the Debugger implementers: See original PR: #7212. |
Was this it?
Given that you can set the port manually, wouldn't debuggers have to be able to determine which protocol was being used with 100% certainty? |
The issue is that some debuggers support both the old protocol and new, and when a user requests that the debugger attach to a running process at port 5858, the debugger has no way of knowing with protocol to use. I think this was originally requested by the VSCode folks, but I can't seem to find the discussion (/cc @joshgav, @nojvek). |
Discussion on side-by-side ongoing at #8464, would appreciate input from you all there. |
/cc @nodejs/diagnostics |
This commit adds a test for the debug port value in cluster workers using the inspector debugger. Refs: nodejs#8201 Refs: nodejs#8386 Refs: nodejs#8550 PR-URL: nodejs#8958 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Ilkka Myller <ilkka.myller@nodefield.com>
Checklist
make -j4 test
(UNIX), orvcbuild test nosign
(Windows) passesAffected core subsystem(s)
inspector
Description of change
This commit consolidates the debugging port used by the inspector and Node's legacy debugger. This eliminates any chance of the two debuggers working side by side, but the inspector is currently an unofficial feature, and the legacy debugger should eventually be removed in favor of it.
Fixes: #8201