Vscode: debugging 'continue' shortcut stopped working, tries to relaunch debugging task

Created on 24 Sep 2019  ·  2Comments  ·  Source: microsoft/vscode


  • VSCode Version: 1.39.0-insider, 9f6a745027fc7b2a12495970f64625e24f410224
  • OS Version: Darwin x64 16.7.0

Steps to Reproduce:

  1. Using f5 to cause vscode to run a debug session on a test in my project using the following config.
{
    "type": "node",
    "request": "launch",
    "name": "Mocha Current",
    "program": "${workspaceFolder}/node_modules/mocha/bin/_mocha",
    "args": ["${file}", "--timeout", "999999", ],
    "internalConsoleOptions": "openOnSessionStart"
}
  1. stop on a breakpoint, previously pressing f5 would cause the continue command to be executed, and the breakpoint to be released. Now I'm just getting an error There is already a debug configuration "Mocha Current" running. and the breakpoint remains as is. I did not change any of the keyboard shortcuts, and see both actions (start debugging and continue) bound to f5


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

bug debug verified

Most helpful comment

Yeah I totally broke this. Sorry about that! The fix will be in next insiders.
Thanks for using insiders and for providing feedback, really appreciate it!

All 2 comments

I'm hitting this as well, debugging a VSCode extension.

Version: 1.39.0-insider (user setup)
Commit: 9f6a745027fc7b2a12495970f64625e24f410224
Date: 2019-09-24T05:26:22.699Z
Electron: 6.0.9
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: Windows_NT x64 10.0.18362

Yeah I totally broke this. Sorry about that! The fix will be in next insiders.
Thanks for using insiders and for providing feedback, really appreciate it!

Was this page helpful?
0 / 5 - 0 ratings