-
Notifications
You must be signed in to change notification settings - Fork 136
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
Restart button not working #1561
Comments
Looks like the extension does not act properly (or not listen to it at all) when a debug session restarts. |
FWIW it used to work fine. I just upgraded to VSCode 1.77 so maybe that’s related? |
Interesting, will take a look! |
There is an
When running a test, the extension will start a local socket server communicate with the runner to get the test results. It makes sense to me that, when restart the runner, the socket connection will be killed, and this error appears. Do you still remember which version of VS Code was used last time when this |
I upgraded this week from 1.75.1, but I’m not sure I remember the last time it worked for sure. |
Hello, I have had this same problem since around April (also after a VS-Code update). Is there a fix for this problem? |
I have the same problem here; are there any plans for a fix? :-) |
A temporary workaround is this keyboard binding: {
"key": "cmd+r",
"command": "runCommands",
"args": {
"commands": [
{
"command": "workbench.action.debug.stop",
},
{
"command": "testing.debugLastRun",
}
]
},
"when": "inDebugMode"
}, |
I tried a pre-release and a release version (v0.38.2) with VSCode 1.77.3. Running a test from code (little green icons) or the test view works, but if you pause and then press "restart" (Ctrl-Shift-F5) in the little floating window it stops running the current test but doesn't restart. I see threads in the debug view but they are just hanging and eventually time out and exit. The test is not restarted.
The text was updated successfully, but these errors were encountered: