-
Notifications
You must be signed in to change notification settings - Fork 28.1k
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
Extensions issue: update / reinstallation #107997
Comments
I was having this issue too, so I did a bit of digging. The change causing this was introduced in 1.49.1-1, in which the Arch packagers switched the marketplace to Open VSX. https://git.archlinux.org/svntogit/community.git/commit/trunk?id=b62a02ec645f16528c0269faf12e362a55efda75 A temporary workaround for this is to use the prior version: The proper solution for this is to reach out to the extension's maintainers and ask them to publish to Open VSX. See https://www.eclipse.org/community/eclipse_newsletter/2020/march/1.php (Ctrl + F for |
Thanks for these information! I suspected it was related to the last version, but I didn't know where to look to find what had changed. I did not know OpenVSX ... I see this is what is used by VS Codium. So in the end, both are using the same marketplace now. I understand for VS Codium, a little less for Code - OSS. Even if I understand the interest, deciding to no longer support Microsoft's marketplace risks limiting the visibility of small open source projects ... I don't think I'm the only one who doesn't know OpenVSX. I just tested. By posting my theme to OpenVSX, it is now available in Code! If anyone has the same problem, another temporary workaround: go to the Marketplace, search for the extension, then click "Download extension". All that remains is to install it in Code using the Anyway, it looks like this isn't a "problem" from VS Code itself, but from Archlinux, so I guess I can close this issue. Thanks again. |
Hello,
As of today, I have encountered a problem with the extensions of VS Code.
I published my own theme on the marketplace a few months ago (
armandphilippot.coldark
). So far, I had no problems updating it. Today I am doing a new update. Everything is going smoothly. I wait. Unable to update theme in VS Code. The option "Install another version" remains grayed out.I switch to Windows, open VS Code, and the extension updates with no problem. The problem therefore seems to come from the VS Code version on Linux, at least Manjaro which is my distribution.
I tried uninstalling my theme to reinstall it. VS Code cannot find it. It is however available on the marketplace, and the Windows version finds it. I tried to install it through the terminal, the result is the same. I first thought of a corrupted package ... I uninstalled another extension to test. Once uninstalled, I cannot reinstall it. The "Install" option does not appear in the open window of the extension (displayed before uninstallation). If I search for the theme again, VS Code cannot find it. In both cases, it was a theme (New Moon by Tania Rascia for the second). So I tested with another type of extension (Preview on Live Server ... I cannot remember the publisher name) and the result is the same.
Here is the information provided by the "About" menu in "Help":
Steps to Reproduce:
For step 2, if I replace it with:
code --install-extension armandphilippot.coldark
The result is the same: Extension 'armandphilippot.coldark' not found.
Here is the output in the terminal:
If that helps, here's what fits into the console of Developer Tools:
Also note: yesterday there were many updates on Manjaro including VS Code. In the pacman logs, I see "1.48.2-1 -> 1.49.1-1" for
code
. The bug must be related to this update since I never had a problem before ...Edit: This problem only happens with an extension that I just uninstalled. Those which have not been installed do offer an "Install" option.
Thanks in advance,
Do not hesitate to ask me for additional information if necessary ... I have tried to be as exhaustive as possible.
Armand.
The text was updated successfully, but these errors were encountered: