Intro:
Steps to Reproduce:
code-insiders .[main 2019-06-23T15:41:16.497Z] update#setState idle
[main 2019-06-23T15:41:46.501Z] update#setState checking for updates
[main 2019-06-23T15:42:02.481Z] update#setState idle
code-insiders . --disable-extensions, launching with code . opens up regular vs code (doesn't leak, but also has no native WSL support). So, does this issue occur when all extensions are disabled? Yes!My Path environment variables for code and code-insiders:
which code-insiders
/c/Users/[me]/AppData/Local/Programs/Microsoft VS Code Insiders/bin/code-insiders
which code
/c/Program Files/Microsoft VS Code/bin/code
My WSL is based on the official Ubuntu 18.04, setup with LxRunOffline
code-insiders . from WSL worked until the last week. So this issue didn't occur before the latest version of code-insiders.(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:
Thanks @vscodebot, these issues do not seem to be related to my bug described above.
@Sieboldianus I believe I have the same issue you are describing.
The error has been fixed with the latest update. Thank you!
Just tested, it works! Many thanks!