Skip to content

Conversation

@joshkel
Copy link
Contributor

@joshkel joshkel commented Jan 2, 2024

If the inspector is already running, then ANR should be able to (re)use that, instead of opening it itself.

Fixes #10024

Before submitting a pull request, please take a look at our
Contributing guidelines and verify:

  • If you've added code that should be tested, please add tests.
  • Ensure your code lints and the test suite passes (yarn lint) & (yarn test).

If the inspector is already running, then ANR should be able to (re)use that, instead of opening it itself.

Fixes #10024
Copy link
Member

@AbhiPrasad AbhiPrasad left a comment

Choose a reason for hiding this comment

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


const testScriptPath = path.resolve(__dirname, 'basic.js');

childProcess.exec(`node --inspect ${testScriptPath}`, { encoding: 'utf8' }, (_, stdout) => {

Check warning

Code scanning / CodeQL

Shell command built from environment values

This shell command depends on an uncontrolled [absolute path](1).
@joshkel
Copy link
Contributor Author

joshkel commented Jan 2, 2024

@AbhiPrasad Done. Thank you.

@AbhiPrasad AbhiPrasad merged commit 1cd771a into getsentry:develop Jan 2, 2024
@joshkel joshkel deleted the anr-inspector branch January 3, 2024 00:37
anonrig pushed a commit that referenced this pull request Jan 3, 2024
If the inspector is already running, then ANR should be able to (re)use
that, instead of opening it itself.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ANR error if Node is run with --inspect

2 participants