sqlite-viewer-vscode
sqlite-viewer-vscode copied to clipboard
Can't seem to update to latest version with OpenVSX
2024-10-23 08:46:14.588 [info] Extension host (Remote) is responsive.
2024-10-23 08:48:29.299 [info] Getting Manifest... qwtel.sqlite-viewer
2024-10-23 08:48:30.166 [info] Installing extension: qwtel.sqlite-viewer
2024-10-23 08:48:30.359 [info] Request to 'https://open-vsx.org/vscode/asset/qwtel/sqlite-viewer/0.8.6+web/Microsoft.VisualStudio.Code.WebResources/extension' failed with status code 404
2024-10-23 08:48:30.359 [warning] Error while fetching extension resources list Error
2024-10-23 08:48:30.538 [info] Request to 'https://open-vsx.org/vscode/asset/qwtel/sqlite-viewer/0.8.6+web/Microsoft.VisualStudio.Code.WebResources/extension/package.json' failed with status code 404
2024-10-23 08:48:30.539 [error] Error while installing the extension qwtel.sqlite-viewer Error while fetching manifest from the location 'https://open-vsx.org/vscode/asset/qwtel/sqlite-viewer/0.8.6%2Bweb/Microsoft.VisualStudio.Code.WebResources/extension'. Error
2024-10-23 08:48:30.550 [error] Error: Error while fetching manifest from the location 'https://open-vsx.org/vscode/asset/qwtel/sqlite-viewer/0.8.6%2Bweb/Microsoft.VisualStudio.Code.WebResources/extension'.
Thanks for keeping me updated on the openVSX side of things. It appears this affects the target=web version only. I've tried installing it in a Google IDX workspace and it worked as intended.
There are some issues that seems related: https://github.com/eclipse/openvsx/issues/575, https://github.com/eclipse/openvsx/issues/744. Perhaps it can be resolved from the openvsx side.
Those error messages from IDX. Strange it worked for you.
It depends on the cpu architecture of the workspace. In my case it happened to be something like linux-x86 and pulling those from openvsx seems to work. Yours seems to be web, which is apparently broken (funny enough, when I updated my publishing script just now, copilot autocompleted if (tool = "osvx" to && target = "web") continue. It appears I'm not the first one to encounter this..)
For the current point release I've skipped the web version, and instead published one without a target specifier ("universal"). With a bit of luck, it will fetch that one instead.
Seems to have worked, thanks.
Wow very cool. Surprised it worked. Thanks for confirming.