-
Notifications
You must be signed in to change notification settings - Fork 147
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
WSL issue? "Make sure you use the full extension ID, including the publisher, e.g.: ms-dotnettools.csharp" #594
Comments
Would you like to provide the output of:
on both Windows and WSL |
Windows:
On an Ubuntu-20.04 WSL:
On an Ubuntu-22.04 WSL (no output for the command):
On a CentOS 7.9 install:
On an AlmaLinux 8 install:
|
For reference, on the AlmaLinux WSL:
This AppData directory appears to be from my Windows homedir, |
It seems that when you invoke the
Topgrade does not expect this output, it expects a list of extensions: $ code --list-extensions
GitHub.github-vscode-theme
rust-lang.rust-analyzer
teabyii.ayu
vscodevim.vim See the source code here: Lines 327 to 349 in 41c6d1c
This is not the first WSL issue we have, see #526, I currently don't have a good idea on how we can work around this, please disable it within your WSL for now |
Basically you can run any Windows executable from WSL. |
Yeah, I am aware of this, all these Windows binaries are in WSL's |
Erroneous Behavior
I think topgrade under my Ubuntu WSL installs detects that I have Visual Studio Code installed ..under Windows..
And then tries to parse a bunch of errors into extension names. Some of entries have meaningful text out of some error message.
Expected Behavior
Steps to reproduce
Possible Cause (Optional)
Problem persists without calling from topgrade
Did you run topgrade through
Remote Execution
If yes, does the issue still occur when you run topgrade directlly in your
remote host
Configuration file (Optional)
Additional Details
Operation System/Version
Installation
Topgrade version (
topgrade -V
)Verbose Output (
topgrade -v
)The text was updated successfully, but these errors were encountered: