You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is probably an OpenVSX bug, see #11080. Last time I checked, it was serving a RA version from around October. We do try to publish it there, but we get a server error and there's no-one who can look into it. I'm quite surprised that you're getting 0.3.1194, that's only 3 weeks old. Did you really install it from the marketplace?
In addition, I suspect that OpenVSX somehow drops the executable bit on that file. It's not their packaging tool -- we publish the same VSIX on the Code Marketplace --, so something must be happening afterwards. We could reset it from the extension, but:
that's a workaround for a server-side bug
on a server where we can't even publish the extension (so our code change wouldn't even reach users AFAICT)
It looks like the rust-stable Sdk Extension is downloading the latest version of the rust-analyzer, so I am wondering if that is where the newer version 0.3.1194 is coming from instead of the rust-analyzer VSCode extension. org.freedesktop.Sdk.Extension.rust-stable//21.08
So maybe this is a Flatpak bug that isn't setting version 0.3.1194 to be executable?
Failed to execute /home/userName/.var/app/com.visualstudio.code-oss/config/Code - OSS/User/globalStorage/matklad.rust-analyzer/rust-analyzer-x86_64-unknown-linux-gnu
Fixed by adding permission to rust-analyzer-x86_64-unknown-linux-gnu to be executable.
Should this file be set as executable when the extension is installed?
rust-analyzer version: rust-analyzer 0.3.1194-standalone
rustc version: rustc 1.63.0
relevant settings:
Operating System: Manjaro Linux
KDE Plasma Version: 5.25.5
KDE Frameworks Version: 5.97.0
Qt Version: 5.15.5
Kernel Version: 5.15.65-1-MANJARO (64-bit)
Flatpak list
The text was updated successfully, but these errors were encountered: