| Git Clone URL: | https://aur.archlinux.org/vscodium-bin-features.git (read-only, click to copy) |
|---|---|
| Package Base: | vscodium-bin-features |
| Description: | Unblock some features in VSCodium |
| Upstream URL: | https://github.com/microsoft/vscode |
| Licenses: | unknown |
| Conflicts: | vscodium-bin-features |
| Provides: | vscodium-bin-features |
| Submitter: | sperg512 |
| Maintainer: | None |
| Last Packager: | silverhikari |
| Votes: | 17 |
| Popularity: | 0.091914 |
| First Submitted: | 2021-05-10 18:00 (UTC) |
| Last Updated: | 2023-10-08 13:10 (UTC) |
Just chiming in. I was still having trouble after reinstalling vscodium-bin, vscodium-bin-features and vscodium-bin-marketplace altogether.
It turns out line 90 of /opt/vscodium/bin/resources/app/product.json was missing a bunch of text.
So I replaced
"https://open-vsx.org"
],
With
"linkProtectionTrustedDomains": ["https://open-vsx.org"],
Everything is working fine again.
bkb, I understand, but it's important to remember this is the Arch USER repository. I'm just a user of the package who came along and noticed it was broken and submitted a patch. The issue with the broken file sticking around so much has to do with the way pacman caches stuff. I've just submitted a patch to the maintainer which falls back to fetching a fresh copy of product.json from github.
Sorry if I'm harsh, maybe I'm to used to repeat already said information, even more last days, that plus some other things doesn't help. Maybe the faulty files come from my part, it's just that I don't find normal that the wrapper doesn't remove/reinstall files, especially since they are not configuration one, not in home folder. But maybe it's the package too, but in that case, everyone should experience the problem, or maybe a lot of people
But I'll try your pushes to see. It's curious that badly formated JSON still happen after multiple correctives from all bin packages. Something happened in the provider part who has broken all these packages at once
bkb, I suspected it might be necessary to do what you've suggested when I submitted the patch to begin parsing the file in python rather than using regexes, but I wasn't sure. I'll submit a patch tomorrow which does what you've suggested should the file on the system fail to parse.
Like you've read in my link "uninstall and reinstall vscodium-bin and vscodium-bin-marketplace. then try to install this package again" is exactly what has been done, and this is the problematic package. So yeah, to prove that "you are having problems with the installation step with it giving a decoder error", you can "uninstall and reinstall vscodium-bin and vscodium-bin-marketplace. then try to install this package again" but to get this package to work it's not the right thing to do, the right thing for this package is to be corrected, or to rewrite all his files upon un/installing
if you are having problems with the installation step with it giving a decoder error, you need to uninstall and reinstall vscodium-bin and vscodium-bin-marketplace. then try to install this package again.
Getting the following error with the current revision (385c507d60e6): sed: can't read +: No such file or directory
Pinned Comments
silverhikari commented on 2023-01-28 15:24 (UTC) (edited on 2023-01-28 18:50 (UTC) by silverhikari)
if you are having problems with the installation step with it giving a decoder error, you need to uninstall and reinstall vscodium-bin and vscodium-bin-marketplace. then try to install this package again.