-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[dotnet, golang] Connot access to extension SDK despite it being installed and FLATPAK_ENABLE_SDK_EXT being used #434
Comments
Try downgrading to the
Then when running
I have overrides set to I do not need to pass in the env.
|
Both works with the 22.08 branch. Is it normal or is there a need for a fix ? |
It's because this flatpak is built upon the See the source for com.visualstudio.code.yaml showing the |
Would have been great if you have also updated the README.md |
Looks like #473 this merge resolves this issue. |
Until the next runtime major update. It is kinda the problem with Flatpak extension. Is it doesn't know for which app we are installing the extension, it just instal the latest one.
Maybe we should create our own extension that just pulls the correct extension, for the correct runtime. If we update this in the documentation, we'll have to continue doing it every times we update the runtime. |
I tried to use the PHP 8.2 SDK extension (22.08 branch) and had the same problem. |
I installed VSCode through Flatpak, and followed the instruction in the first run text file, but VSCode as well as VScode-OSS both do not detect the Flatpak sdk extension.
I tried both
FLATPAK_ENABLE_SDK_EXT=dotnet
andFLATPAK_ENABLE_SDK_EXT=dotnet7
beforeflatpak run com.visualstudio.code
, both returnedRequested SDK extension "dotnet" is not installed
Installed SDKs:
Same problem with the golang extenssion and
FLATPAK_ENABLE_SDK_EXT=golang
In all cases
/usr/lib/sdk/
is empty.Edit: the command
$ find / -iname dotnet
returns no result when executed inside the container.Edit2: Something noteworthy I ended up finding is that the dotnet6 sdk do work as intended, but both dotnet5, dotnet7 and golang don't.
The text was updated successfully, but these errors were encountered: