Valid position of --inspect argument during Node.js attachment

[Flopriant]

Does this issue occur when all extensions are disabled?: Yes

• VS Code Version: 1.89.1
• OS Version: Windows_NT x64 10.0.22631

Steps to Reproduce:

1. Do a program in Python 3.9.13 64-bit
2. Press F5
3. Nothing happens at all

[mikepaszkiewicz]

I am also getting this, right after updating to the below version, running the below launch.json config. After clicking the process to inspect, the 'Call Stack' section shows RUNNING for around 10 seconds before disappearing.

Same behavior disabling all extensions and restarting.

Inspector shows error:

Error: Could not connect to debug target at http://localhost:9229: Could not find any debuggable target
    at /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/ms-vscode.js-debug/src/extension.js:110:38167
    ...

Version: 1.89.0 (Universal)
Commit: b58957e67ee1e712cebf466b995adf4c5307b2bd
Date: 2024-05-01T02:10:10.196Z (2 wks ago)
Electron: 28.2.8
ElectronBuildId: 27744544
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Darwin arm64 23.4.0

launch.json

  "configurations": [
    {
      "name": "Attach by Process ID",
      "processId": "${command:PickProcess}",
      "request": "attach",
      "skipFiles": ["<node_internals>/**"],
      "outputCapture": "std",
      "type": "node"
    },
]

[roblourens]

@Flopriant can you open an issue on the Python repo?

@mikepaszkiewicz it looks like maybe your program just failed to start?

[mikepaszkiewicz]

@roblourens the program i'm trying to connect to is definitely running, as I can select it from the process picker and reach via curl.

also just confirmed downgrading to 1.87.2 allows the debugger to conenct

Version: 1.87.2
Commit: 863d2581ecda6849923a2118d93a088b0745d9d6
Date: 2024-03-08T15:20:57.520Z (2 mos ago)
Electron: 27.3.2
ElectronBuildId: 26836302
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: 11.8.172.18-electron.0
OS: Darwin arm64 23.4.0

[connor4312]

I think in your case you have an --inspect argument, but it's in the wrong place and it's not handled by Node.js, it's handled by your process. In microsoft/vscode-js-debug#1987 I made a change so that we don't try to force the process into debug mode if --inspect is already present (since this caused issues in another case.) For you --inspect is present just in the wrong place, it need to be before the script to execute.

We could also be smarter about this in the debugger.

[mikepaszkiewicz]

@connor4312 Awesome - changing from node build/server/server.js --inspect to node --inspect build/server/server.js appears to have done the trick!

Also of note - removing the --inspect flag from the script entirely fixed the issue as well as far as I can tell, so assume it's perhaps happening behind the scenes?

[connor4312]

If the process is not launched with --inspect we can (usually) force it into inspect mode, but we skip that code path if we see it's already launched with --inspect

[connor4312]

Your issue is unrelated, please open a bug for the Python extension. This issue is regarding the JavaScript debugger.