You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesverifiedVerification succeeded
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
The text was updated successfully, but these errors were encountered:
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
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!
isidorn
added
bug
Issue identified by VS Code Team member as probable bug
debug
Debug viewlet, configurations, breakpoints, adapter issues
labels
Sep 25, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesverifiedVerification succeeded
Steps to Reproduce:
f5
to cause vscode to run a debug session on a test in my project using the following config.f5
would cause thecontinue
command 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 debugging
andcontinue
) bound tof5
Does this issue occur when all extensions are disabled?: Yes
The text was updated successfully, but these errors were encountered: