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
@isidorn I've seen something like this too. For me it typically happens for the same debug type: first I run a launch config "test", then I switch to launch config "server" and press the green start button. Later, when waiting for the server to startup, I notice that the tests are running again...
I believe this is a timing issue (race condition). While a debug session is running, it should not be possible to switch the launch config. But sometimes it seems to be possible. However, when the debug sessions ends the new launch config is switched back to old launch config.
isidorn
added
the
bug
Issue identified by VS Code Team member as probable bug
label
Sep 8, 2016
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:
Unit Test
in debug viewlet, and enable a breakpoint that will be hit.Launch VSCode
(which hastype: chrome
).Unit Test
instead of runningLaunch VSCode
or produce an error saying "Debug typechrome
is not supported".The text was updated successfully, but these errors were encountered: