mirror of
https://github.com/VSCodium/vscodium.git
synced 2026-04-09 20:50:20 -05:00
Option to disable "Extension not found on marketplace" warning #1028
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @lamyergeier on GitHub.
Originally assigned to: @daiyam on GitHub.
Describe the bug
I migrated from Vscode to Vscodium and copied extensions as follows
cp -R ~/.vscode/extensions ~/.vscode-oss/extensions. I get the following error whenever I open vscodium:Is it possible to disable this error?
Please confirm that this problem is VSCodium-specific
Please confirm that the issue/resolution isn't already documented
Desktop (please complete the following information):
@lefterisgar commented on GitHub:
I have this issue too and it is really frustrating. I had managed to disable it in previous versions by placing the extension name in
unwantedRecommendationsbut after a clean install there is no way to fix it.@lamyergeier commented on GitHub:
@stripedpajamas Could you please disable this warning? It pops out everytime I open vscodium!
@lamyergeier commented on GitHub:
This is false!
@lefterisgar commented on GitHub:
WORKAROUND: Erase all extensions from
recommendationsin .vscode/extensions.json:Then make the file read-only. It seems to work.
@shanmukhateja commented on GitHub:
Hi,
Could you try using VSCode marketplace by following the steps mentioned here ?
As for the notification, you should be able to disable it by clicking on the dropdown arrow to the right and selecting the appropriate menu action, haven't seen it before though.
@daiyam commented on GitHub:
+1
@github-actions[bot] commented on GitHub:
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment, and we'll keep it open. If you have any new additional information, please include it with your comment!
@github-actions[bot] commented on GitHub:
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment, and we'll keep it open. If you have any new additional information, please include it with your comment!
@lefterisgar commented on GitHub:
This issue is still affecting me.
@GitMensch commented on GitHub:
@daiyam: Could you add a setting to never show this again like you did for the eol-banner?
Note: for me this is not an issue - I do have setup several extensions to be recommended that cannot be found in the marketplace - on each start of vscodium (commonly once per day) I get a very small notification about that - which does remind me to check for these extensions' updates manually in their repos (or use gitpod to build them on my own); but if people would not like to be reminded it may be nice to have a "don't remind me" option.
The option in both places could be sent upstream, too.
@GitMensch commented on GitHub:
Note @Crystal-RainSlide: your point "a project's extension recommendation" [would also apply to .code-workspace btw] is relevant but actually another one as the original; which was "copy the vscode settings into vscodium when starting using that - and see a lot of warnings each time".
@Crystal-RainSlide commented on GitHub:
There could be extensions only on Open-VSX but not Microsoft's marketplace. It will be viable for a ignore / "don't remind me" patch be sent upstream.
Note to project owners:
.vscode/extensions.jsonis actually kinda annoying, even without this "extension not found" issue - it just ask everyone who did not install EVERY extension it recommends to do so - everytime they open your project fresh, or forget to click the "Don't show" button.Try leave only the strict necessary extensions in
.vscode/extensions.json. Put others to somewhere else like the README.@github-actions[bot] commented on GitHub:
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment, and we'll keep it open. If you have any new additional information, please include it with your comment!
@GitMensch commented on GitHub:
Needs to be rechecked, if this still happens then we should try to add the "ignore" button.
@github-actions[bot] commented on GitHub:
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment, and we'll keep it open. If you have any new additional information, please include it with your comment!
@GitMensch commented on GitHub:
So I've understood that @daiyam, who self-assigned this issue, wanted to add this setting. Right?
@github-actions[bot] commented on GitHub:
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment, and we'll keep it open. If you have any new additional information, please include it with your comment!
@GitMensch commented on GitHub:
@lamyergeier can you please recheck what the current behavior is?