Vim Extension won't work if marketplace is down
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 6
Description
Describe the bug
Yesterday the website https://open-vsx.org/ was down. This made the plugin throw an exception and not work. This is frustrating because as a user of a vim plugin I just want to get my work done and not have multiple points of failures that are beyond my control.
After plugin is installed should work even without internet access or market place going down.
Console logs:
[2022-09-29 20:42:57.933] [exthost] [info] ExtensionService#_doActivateExtension vscodevim.vim, startup: false, activationEvent: '*'
[2022-09-29 20:42:58.040] [exthost] [error] Activating extension vscodevim.vim failed due to an error:
[2022-09-29 20:42:58.063] [exthost] [error] Error: Service Unavailable
at S._loadCommonJSModule (../../../vs/workbench/api/worker/extensionHostWorker.js:76:64278)
at async Promise.all (index 0)
at async f._activate (../../../vs/workbench/api/worker/extensionHostWorker.js:68:8225)
at async f._waitForDepsThenActivate (../../../vs/workbench/api/worker/extensionHostWorker.js:68:8167)
at async f._initialize (../../../vs/workbench/api/worker/extensionHostWorker.js:68:7531)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Start by reproducing extension activation while https://open-vsx.org/ is unavailable, then trace the activation path associated with the logged Service Unavailable error. Done means the installed Vim extension activates and remains usable without internet access or a working marketplace.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100