Skip to content
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

[Suggestion] Add option to allow setting process name based on --inspect-brk=0 random port #28998

Closed
Jamesernator opened this issue Aug 6, 2019 · 2 comments
Labels
feature request Issues that request new features to be added to Node.js. inspector Issues and PRs related to the V8 inspector protocol stale

Comments

@Jamesernator
Copy link

Currently when using --inspect-brk=0 tools like VSCode are unable to effectively auto attach debuggers to them.

It is also particularly hard to have a cross platform way of detecting node processes that can be attached to when NODE_OPTIONS= is used.

I'd like to propose adding another option such as --inspect-set-process-title=pattern which sets the process title to the given pattern where some things like the websocket name and port can be replaced in the pattern.

e.g.:

# Where %port% gets replaced with the debugging port
$ node --inspect-brk=0 --inspect-set-process-title="node:vscode-auto-attach-port=%port%"
# Or where %websocketUrl% is replaced with the websocket url
$ node --inspect-brk=0 --inspect-set-process-title="node:vscode-auto-attach-w=%websocketUrl%

This could also work with the existing --title option when using --inspect-brk, I don't have a strong preference for a specific solution.

@Jamesernator Jamesernator changed the title Add option to --inspect-brk=0 to allow setting process name based on randomly chosen port Add option to allow setting process name based on --inspect-brk=0 random port Aug 6, 2019
@Jamesernator Jamesernator changed the title Add option to allow setting process name based on --inspect-brk=0 random port [Suggestion] Add option to allow setting process name based on --inspect-brk=0 random port Aug 6, 2019
@bnoordhuis bnoordhuis added feature request Issues that request new features to be added to Node.js. inspector Issues and PRs related to the V8 inspector protocol labels Aug 6, 2019
@github-actions
Copy link
Contributor

There has been no activity on this feature request for 5 months and it is unlikely to be implemented. It will be closed 6 months after the last non-automated comment.

For more information on how the project manages feature requests, please consult the feature request management document.

@github-actions github-actions bot added the stale label Feb 25, 2022
@targos targos moved this to Pending Triage in Node.js feature requests Feb 25, 2022
@targos targos moved this from Pending Triage to Stale in Node.js feature requests Feb 25, 2022
@github-actions
Copy link
Contributor

There has been no activity on this feature request and it is being closed. If you feel closing this issue is not the right thing to do, please leave a comment.

For more information on how the project manages feature requests, please consult the feature request management document.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Issues that request new features to be added to Node.js. inspector Issues and PRs related to the V8 inspector protocol stale
Projects
None yet
Development

No branches or pull requests

2 participants