-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Adopt proposed API for test debug restart #23752
Comments
here is the core issue we are using to make these changes: microsoft/vscode#214486 |
Potential bug: It seems that onTerminateDebugSession gets called for all runInstances known to the debugger from the reload state. See logs I recorded with these random distinct numbers to differentiate the run instances. You can see my first runInstance #426 is created then canceled (this is bc I have reloaded which we talked about was the right behavior). Then the reload spawns a new process right after (runInstance #721) which I never cancel or anything as the user but you can see onDidTerminateDebugSession is called on it either way. What is also interesting is the other runInstance numbers called for onDidTerminateDebugSession were from a previous run I had made when trying this same process before (#530 and #994). So those instances should be completely gone but they come back and get called again. Once I reload my vscode window previous instances disappear but as long as I am in a session, only instances are called again. From this it seems like onDidTerminateDebugSession is being called too many times and specifically is called too early for my regenerated instance on reload which causes a bug. Logs from Run |
this was a tracking issue- the verification should be done on related bugs like: #20520 |
No description provided.
The text was updated successfully, but these errors were encountered: