-
Notifications
You must be signed in to change notification settings - Fork 38.2k
Closed
microsoft/azuredatastudio
#7404Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesDebug viewlet, configurations, breakpoints, adapter issuesverifiedVerification succeededVerification succeeded
Milestone
Description
- VSCode Version: 1.39.0-insider, 9f6a745
- OS Version: Darwin x64 16.7.0
Steps to Reproduce:
- Using
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"
}- stop on a breakpoint, previously pressing
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 tof5
Does this issue occur when all extensions are disabled?: Yes
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesDebug viewlet, configurations, breakpoints, adapter issuesverifiedVerification succeededVerification succeeded