- VSCode Version: 1.39.0-insider, 9f6a745
- OS Version: Darwin x64 16.7.0
Steps to Reproduce:
- 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"
}
- 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
Steps to Reproduce:
f5to 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" }f5would cause thecontinuecommand to be executed, and the breakpoint to be released. Now I'm just getting an errorThere 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 debuggingandcontinue) bound tof5Does this issue occur when all extensions are disabled?: Yes