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
We can use the launch task "Run Tests" to create second instance of vscode and run tests there (and log results to debug console):
With vscode 1.53.2 this stopped working for me (Debug console stays empty). Our logging (when building + running the extension) could also be affected.
Downgrading vscode fixed it. Also, there are changes around this topic in the release, so its plausible: microsoft/vscode#115874
I don't know if we need to adapt or create an issue with vscode. I just wanted to bring it up as info.
The text was updated successfully, but these errors were encountered:
We can use the launch task "Run Tests" to create second instance of vscode and run tests there (and log results to debug console):
With vscode 1.53.2 this stopped working for me (Debug console stays empty). Our logging (when building + running the extension) could also be affected.
Downgrading vscode fixed it. Also, there are changes around this topic in the release, so its plausible:
microsoft/vscode#115874
I don't know if we need to adapt or create an issue with vscode. I just wanted to bring it up as info.
The text was updated successfully, but these errors were encountered: