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

debugging 'continue' shortcut stopped working, tries to relaunch debugging task #81373

Closed
tomrav opened this issue Sep 24, 2019 · 2 comments · Fixed by microsoft/azuredatastudio#7404
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues verified Verification succeeded

Comments

@tomrav
Copy link

tomrav commented Sep 24, 2019

  • VSCode Version: 1.39.0-insider, 9f6a745
  • 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

@tomrav tomrav changed the title debugging 'continue' shortcut stopped working, tries to relaunch task debugging 'continue' shortcut stopped working, tries to relaunch debugging task Sep 24, 2019
@bwateratmsft
Copy link
Contributor

bwateratmsft commented Sep 24, 2019

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

@isidorn
Copy link
Contributor

isidorn commented Sep 25, 2019

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!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues verified Verification succeeded
Projects
None yet
4 participants