The tarballs provided by Microsoft are 20mb larger than the debs for the same release (I imagine because the deb uses xz compression):

-rw-rw-r-- 1 nick nick 44M Jan 31 13:01 code_1.19.3-1516876437_amd64.deb
-rw-rw-r-- 1 nick nick 45M Jan 31 13:01 code_1.19.3-1516876497_i386.deb
-rw-rw-r-- 1 nick nick 64M Jan 31 13:05 code-stable-code_1.19.3-1516876437_amd64.tar.gz
-rw-rw-r-- 1 nick nick 65M Jan 31 13:06 code-stable-code_1.19.3-1516876497_i386.tar.gz

This considerably outweighs the savings gained for users from removing the deb tools from the package.

i have multiple sdk install the machine at user level, load through PATH at zshrc file...
eg. flutter sdk at ~/.flutter-sdk, and android sdk at ~/.android-sdk

everything work fine on rpm installed version of vscode... however, the flatpak version of vscode fail to load those defined sdk... is this the problem of vscode extension or problem of flatpak app structure???

VS Code is crashing when it tries to open the native GTK file dialog (at least with Open Folder, Save As, and Open File). This is with version 1.30.1 from Flathub running on Ubuntu 18.04, using Adwaita for widget styles and icons. Unfortunately, I don't know when it started crashing, but I'm confident it can't have been too long.

Running the app from the command line gives me the following output:

$ flatpak run --command=/app/extra/vscode/code com.visualstudio.code 
Gtk-Message: 17:23:41.618: Failed to load module "canberra-gtk-module"
Gtk-Message: 17:23:41.618: Failed to load module "canberra-gtk-module"
[main 17:23:42] update#setState idle
sh: cannot set terminal process group (-1): Inappropriate ioctl for device
sh: no job control in this shell

(code:2): GLib-GIO-CRITICAL **: 17:23:51.185: g_unix_is_system_fs_type: assertion 'fs_type != NULL && *fs_type != '\0'' failed

(code:2): GLib-GIO-CRITICAL **: 17:23:51.185: g_unix_is_system_device_path: assertion 'device_path != NULL && *device_path != '\0'' failed
Cannot upload crash dump: cannot exec /usr/bin/wget
Server response: 
$

I also tried with a fresh config folder, same issue.

Version: 1.30.1
Commit: dea8705087adb1b5e5ae1d9123278e178656186a
Date: 2018-12-18T18:07:32.870Z
Electron: 2.0.12
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
OS: Linux x64 4.15.0-43-generic

.

Hi, I was trying to use the FlatPak version of Visual Studio code, and for the most part it works fine.

I was trying to use CMake with the following extension: https://github.com/vector-of-bool/vscode-cmake-tools

This failed because my project requires CMake > 3.11, but the CMake version packaged in the org.freedesktop.Sdk/x86_64/1.6 SDK is pretty old, namely 3.7.2.

I tried to use the system CMake, but that doesn't work because flatpak mounts the runtimes over the system /usr/bin, even when running with --filesystem=host.

I think there should be a better way for integration for system tools with VSCode.

Apparently it needs this line fs.inotify.max_user_watches=524288 added to /etc/sysctl.conf

I've tried copying binary and libraries to my home still does not work

thanks

Linux distribution and version

Debian 9 strecth

Flatpak version

Flatpak 0.8.9

Description of the problem

microsoft/vscode-cpptools#1550
The fact that the app is virtualized makes it so that you can't run : flatpak run org.godotengine.Godot
or any flatpak command in the integrated terminal of vscode. You can't also use gnome-terminal as your integrated terminal in vscode because of this. This makes it also troublesome when trying to use external apps that are used by the extensions.(i.e. My haxe extensions in vscode can't find haxe in my path even though it is installed).

Haxe is available in /usr/bin/ so I guess vscode should detect it.

Steps to reproduce

• Install vscode with flatpak
• use the integrated terminal of vscode(try with sh/bash) and call flatpak list

Potential solution:

Adding --filesystem=/bin/ access to vscode ? Are there any reasons for not doing this ? What would be the work around.

Tested on Fedora 27, the shipped CJK input methods does not work. Wondering what's wrong

I set bash to be the standard terminal in the settings: "terminal.integrated.shell.linux": "/bin/bash" but it doesn't work. I only have this problem with the flatpak version of vscode. Is this because of flatpaks sandbox?

OS: Kubuntu 18.04 LTS

Visual Studio Code offers to open a project folder with the command-line option:
code .

With the flatpak version of the app, this option is not available for me using Konsole terminal.
Error details (sorry, it's in spanish):

No se ha encontrado la orden «code», quizás quiso decir:
 La orden «cde» del paquete «cde» (universe)
 La orden «ode» del paquete «plotutils» (universe)
 La orden «cobe» del paquete «python-cobe» (universe)
 La orden «tcode» del paquete «emboss» (universe)
 La orden «node» del paquete «nodejs-legacy» (universe)
 La orden «cdde» del paquete «cdde» (universe)
code: no se encontró la orden

Flatpak App version info:

Versión: 1.20.0
Confirmación: c63189deaa8e620f650cc28792b8f5f3363f2c5b
Fecha: 2018-02-07T17:10:15.949Z
Shell: 1.7.9
Representador: 58.0.3029.110
Nodo 7.9.0
Arquitectura x64

Doing this would require the dotnet cli tools in the path.

Here is the output from C/C++ extension:

  /home/jeffshee/.var/app/com.visualstudio.code/data/vscode/extensions/ms-vscode.cpptools-0.20.1/bin/../LLVM/bin/clang-format: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory

OS: Fedora 29

flatpak info com.visualstudio.code 
Ref: app/com.visualstudio.code/x86_64/stable
ID: com.visualstudio.code
Arch: x86_64
Branch: stable
Origin: flathub
Collection ID: org.flathub.Stable
Date: 2019-01-12 23:59:24 +0000
Subject: update appdata (5077c6a9)
Commit: 190dc6a2318ec15ac40f951ade68e784517da4eeb5e218f8652cc71dadd8359e
Parent: 8a5c0d03707f2bff5a69bf8efb849d686366e8dbf357261c2dcbfa6ab02b355d
Location: /var/lib/flatpak/app/com.visualstudio.code/x86_64/stable/190dc6a2318ec15ac40f951ade68e784517da4eeb5e218f8652cc71dadd8359e
Installed size: 3.6 MB
Runtime: org.freedesktop.Sdk/x86_64/18.08
Sdk: org.freedesktop.Sdk/x86_64/18.08

I've tried to use the docker extension but I got the following error:

Unable to connect to Docker, is the Docker daemon running?

Usually this error is fixed by adding the user to the docker group. However this fix does not seem to work in the flatpak version of vscode.

How to reproduce:

1. Open console in Visual Studio Code
2. type: gdb ./<any_executable>
3. run program

Output:

warning: Error disabling address space randomization: Operation not permitted
warning: Could not trace the inferior process.
Error:
warning: ptrace: Operation not permitted
During startup program exited with code 127.

OS: Ubuntu 18.04 (KDE neon)
flatpak version: 1.0.4

I guess flatpak sandbox doesn't provide device access, so programming or debugging with openocd will always fail. Tried with J-LINK and ST-LINK, the result is the same. Is there any easy way how to fix this?

currently i have a configure like below in ~/.zshrc

export JAVA_HOME=/usr/lib/jvm/java

export ANDROID_HOME=$HOME/.android/sdk
export PATH=$PATH:$ANDROID_HOME/tools
export PATH=$PATH:$ANDROID_HOME/tools/bin
export PATH=$PATH:$ANDROID_HOME/platform-tools
export PATH=$PATH:$ANDROID_HOME/emulator

export PATH=$PATH:$HOME/.local/lib/dart-sdk/bin
export PATH=$PATH:$HOME/.pub-cache/bin
export PATH=$PATH:$HOME/.local/lib/flutter/bin

how can i load this on flatpak vscode?

Although zsh is installed on the host OS, visual studio code which is sandboxed does not include zsh.
I guess it should be bound into the sandbox.

Basically, zsh is /usr/bin/zsh on the host OS.

Came from microsoft/vscode#62532

VS Code under flatpack is not workable for complex projects, while with a separate installation everything is fine.

In the OS terminal:

art@artPC:/$ ls /usr/bin/../lib/gcc/
avr  i686-linux-gnu  x86_64-linux-gnu

In the VSCode integrated under flatpack:

sh-4.4$ ls /usr/bin/../lib/gcc/
x86_64-unknown-linux-gnu

There is only one object (really 3) and it has different name - x86_64-unknown-linux-gnu instead correct x86_64-linux-gnu. As result - cannot to build library.

The new stdin feature in VS Code 1.19.0 is clobbering the session restore.

I would like to be able to use code as an executable from the command line much as I can with an rpm install (such as code project_folder to open an instance of VS Code on that folder).

Corollary to this is in shanalikhan/code-settings-sync#617

I'm unable to run one of the extensions when it appears that the extension functions don't get bound correctly. This isn't an issue for any other version of Code that I've tried, is there something that can be changed here to restore usability?

I've upgraded visual studio code with flatpak and since then I can't use it any more. It's always crashing when I try to click on "open folder" or "add workspace" etc

If I run vscode from shell in devel mode:

sh-4.4$ LANG=C /app/extra/vscode/code
Gtk-Message: 19:53:19.760: Failed to load module "pk-gtk-module"
Gtk-Message: 19:53:19.760: Failed to load module "canberra-gtk-module"
Gtk-Message: 19:53:19.760: Failed to load module "pk-gtk-module"
Gtk-Message: 19:53:19.760: Failed to load module "canberra-gtk-module"
[main 7:53:20 PM] update#setState idle
sh: cannot set terminal process group (-1): Inappropriate ioctl for device
sh: no job control in this shell

(code:119): Gtk-WARNING **: 19:53:24.543: Could not load a pixbuf from icon theme.
This may indicate that pixbuf loaders or the mime database could not be found.
**
Gtk:ERROR:../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /run/host/share/icons/Paper/16x16/status/image-missing.png: Error opening file /run/host/share/icons/Paper/16x16/status/image-missing.png: No such file or directory (g-io-error-quark, 1)
Cannot upload crash dump: cannot exec /usr/bin/wget
Server response: 
Abandon (core dumped)

Any idea ? It was working fine before 1.29.

I try to repair, remove/reinstall etc same results.
Using vscode 1.29 from RPM is working fine.

Version: 1.29.0
Commit: 5f24c93878bd4bc645a4a17c620e2487b11005f9
Date: 2018-11-12T07:42:27.562Z
Electron: 2.0.12
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
Architecture: x64

Best regards,
Edouard

Hi,

I originally reported this here: microsoft/vscode#44646

But it appears to be an issue with the Flatpack version of VS Code. It almost appears that the flatpack version is running the integrated terminal in a chrooted environment.

I currently run a Debian machine with vscode installed both as .deb and via flatpak. I have also got the default JDK package installed, which satisfies the requirements for running the vscode-java extension.

The flatpak version keeps throwing an error with the following message "The JAVA_HOME environment variable points to a missing folder", whereas the packaged version does not. I suspect the flatpak confinement prevents vscode from finding the JDK installed on the system.

Would there be an easy way to expose JAVA_HOME to vscode without having to bundle the JDK and / or the vscode-java extension in the flatpak?

Anyone facing this problem?

Failed to launch emulator: emulator: ERROR: x86 emulation currently requires hardware acceleration! Please ensure KVM is properly installed and usable. CPU acceleration status: /dev/kvm is not found: VT disabled in BIOS or KVM kernel module not loaded

› ll /dev/kvm crw-rw-rw-. 1 root kvm 10, 232 Sep 18 19:00 /dev/kvm

I want to install development libraries for Python, but can't install them inside the sandbox. The maintainer of the Atom flatpak made this change for Atom: flathub/io.atom.Atom@761fe88

Is there some way to access system binaries like /usr/bin/go inside sandbox? Many plugins do need system binaries to work properly.

Live Share won't work until these libraries are available in the flatpak package
https://docs.microsoft.com/en-us/visualstudio/liveshare/reference/linux#install-linux-prerequisites

There is an annoying problem with the Ctrl+Shift+E shortcut, that is handled specially by GTK+3 in versions before 3.24. Updating to the recent GTK version should fix it.

I guess this should be fixed in due course by updating the Electron base app, but I'm filing this issue here to provide the motivation and tracking relevant to this application.

When I try to update the Flatpak (with "flatpak update --verbose" in the console) always comes the following error message.

F: Opening system flatpak installation at path /var/lib/flatpak
F: Opening user flatpak installation at path /home/schmidicom/.local/share/flatpak
F: No installations directory in /etc/flatpak/installations.d. Skipping
Looking for updates...
F: Fetching summary file for remote ‘flathub’
F: Transaction: update flathub:app/com.spotify.Client/x86_64/stable[$old]
F: Transaction: update flathub:app/com.valvesoftware.Steam/x86_64/stable[$old]
F: Transaction: update flathub:app/com.visualstudio.code/x86_64/stable[$old]
F: Transaction: update flathub:app/org.kde.elisa/x86_64/stable[$old]
F: Transaction: update flathub:runtime/org.freedesktop.Platform.Compat.i386/x86_64/18.08[$old]
F: Transaction: update flathub:runtime/org.freedesktop.Platform.Locale/x86_64/18.08[$old]
F: Transaction: update flathub:runtime/org.freedesktop.Platform.VAAPI.Intel/x86_64/18.08[$old]
F: Transaction: update flathub:runtime/org.freedesktop.Platform.ffmpeg/x86_64/1.6[$old]
F: Transaction: update flathub:runtime/org.freedesktop.Platform.html5-codecs/x86_64/18.08[$old]
F: Transaction: update flathub:runtime/org.freedesktop.Platform/x86_64/18.08[$old]
F: Transaction: update flathub:runtime/org.freedesktop.Sdk.Locale/x86_64/18.08[$old]
F: Transaction: update flathub:runtime/org.freedesktop.Sdk/x86_64/18.08[$old]
F: Transaction: update flathub:runtime/org.gtk.Gtk3theme.Breeze/x86_64/3.22[$old]
F: Transaction: update flathub:runtime/org.kde.Platform.Locale/x86_64/5.11[$old]
F: Transaction: update flathub:runtime/org.kde.Platform/x86_64/5.11[$old]
F: Transaction: update flathub:runtime/org.kde.elisa.Locale/x86_64/stable[$old]
F: Updating remote metadata for flathub
F: marking op update:runtime/org.kde.elisa.Locale/x86_64/stable resolved to 6644b251cd19b8437f8ee7f512378360c3a367331a14d7dc3febda8e435fb220
F: marking op update:runtime/org.kde.Platform/x86_64/5.11 resolved to 02ede84d3591a5ea8028204d86059bffaccb778159ec53c859bbc60d9e7025e8
F: marking op update:runtime/org.kde.Platform.Locale/x86_64/5.11 resolved to 5c93e19ba8c37fd60d3c47b21d5f5020af83b5d8b0160e34e30597c28e16c38b
F: marking op update:runtime/org.gtk.Gtk3theme.Breeze/x86_64/3.22 resolved to 9c4b6885973221c35d2f357d12b53be9cd36a5f6ddbd102769e7c115b2a70af9
F: marking op update:runtime/org.freedesktop.Sdk/x86_64/18.08 resolved to c3f62b801fec84408ad169b44bcea9b30e2acf7881727045a24b3953ff0de791
F: marking op update:runtime/org.freedesktop.Sdk.Locale/x86_64/18.08 resolved to 19f9cf40d3fe49023dac295a36cd327763ac2e91124a9b011fb24d711389da38
F: marking op update:runtime/org.freedesktop.Platform/x86_64/18.08 resolved to 5ff8a9d6f9a66a25b95aed8f6b0f476531a291738619cf4cfa0bd74e19697f19
F: marking op update:runtime/org.freedesktop.Platform.html5-codecs/x86_64/18.08 resolved to 048b7af42a99ae71de0344fae065045104c00219333e8e46a22f488f61f6bd52
F: marking op update:runtime/org.freedesktop.Platform.ffmpeg/x86_64/1.6 resolved to d757f762489e444551d17223590635d4f4014a36b6fecd73323bf3f95f1aa490
F: marking op update:runtime/org.freedesktop.Platform.VAAPI.Intel/x86_64/18.08 resolved to 06d7699cc7409ed046f79a0c5535796990f345cd99ca4804b33046fdd7c84f09
F: marking op update:runtime/org.freedesktop.Platform.Locale/x86_64/18.08 resolved to 8e297b5ae01eeb036819dc40171e7550e7d7a87af6bf3439efae0e214c8f9ec9
F: marking op update:runtime/org.freedesktop.Platform.Compat.i386/x86_64/18.08 resolved to 32831fd47ad08b04d5574d8b338a7346afb6c64025ce64c6f994e2d283971220
F: marking op update:app/org.kde.elisa/x86_64/stable resolved to 0f24374c81c606093c8ca8ad3766c663a55e882a005a52a4051971f38c749963
F: marking op update:app/com.visualstudio.code/x86_64/stable resolved to 190dc6a2318ec15ac40f951ade68e784517da4eeb5e218f8652cc71dadd8359e
F: marking op update:app/com.valvesoftware.Steam/x86_64/stable resolved to d687358a1396190f3b7aa0a2d47dd24d9c90f1fe241cf97cbdb2b14b334c0635
F: marking op update:app/com.spotify.Client/x86_64/stable resolved to 8f0a500bf0edc7a66c390921bb0ea34506fbd1fbf819edd4760b1b29a331af37
F: Transaction: install/update flathub:runtime/org.freedesktop.Platform.ffmpeg/x86_64/1.6[*]
F: Transaction: install/update flathub:runtime/org.gtk.Gtk3theme.Breeze/x86_64/3.22[*]
F: Transaction: install/update flathub:runtime/org.kde.Platform.Locale/x86_64/5.11[/de]
F: Transaction: install/update flathub:runtime/org.freedesktop.Sdk.Locale/x86_64/18.08[/de]
F: Transaction: install/update flathub:runtime/org.gtk.Gtk3theme.Breeze/x86_64/3.22[*]
F: Transaction: install/update flathub:runtime/org.freedesktop.Platform.html5-codecs/x86_64/18.08[*]
F: Transaction: install/update flathub:runtime/org.freedesktop.Platform.VAAPI.Intel/x86_64/18.08[*]
F: Transaction: install/update flathub:runtime/org.freedesktop.Platform.Locale/x86_64/18.08[/de]
F: Transaction: install/update flathub:runtime/org.gtk.Gtk3theme.Breeze/x86_64/3.22[*]
F: Transaction: install/update flathub:runtime/org.freedesktop.Platform.VAAPI.Intel/x86_64/18.08[*]
F: Transaction: install/update flathub:runtime/org.freedesktop.Platform.html5-codecs/x86_64/18.08[*]
F: Transaction: install/update flathub:runtime/org.kde.elisa.Locale/x86_64/stable[/de]
F: Transaction: install/update flathub:runtime/org.freedesktop.Platform.Compat.i386/x86_64/18.08[*]
Updating in user:
com.visualstudio.code/x86_64/stable flathub 190dc6a2318e
Is this ok [y/n]: y
Updating for user: com.visualstudio.code/x86_64/stable from flathub
F: Loading https://vscode-update.azurewebsites.net/1.30.2/linux-deb-x64/stable using libsoup
[#=                  ] Downloading extra data: 569 Bytes/45.9 MB
(flatpak update:2147): libsoup-CRITICAL **: 16:20:17.599: async_send_request_return_result: assertion 'item->task != NULL' failed
[#=                  ] Downloading files: 1/1 569 Bytes (569 Bytes/s)
Fehler: update com.visualstudio.code/x86_64/stable ist fehlgeschlagen: Während des Herunterladens von https://vscode-update.azurewebsites.net/1.30.2/linux-deb-x64/stable: Server returned status 0: Unknown Error
Fehler: There were one or more errors

My Version:
flatpak-1.0.6 with libsoup-2.65.1 on Gentoo

CC from the Microsoft/vscode repo
CC from the flathub/flathub repo

Issue Type

Bug

Description

• Use Debian Stretch (GNOME + Wayland), everything up-to-date
• Use flatpak from Debian's repos
• Install VS Code using the package (which appears to be officially) distributed at flathub.org
• Start VS Code and try to use Git integration (anything, here git pull as an example) on a repo where you use SSH authentication with a SSH key protected by passphrase
  • Error log (as a side note: /usr/libexec/ssh-askpass does indeed not exist)

git pull
ssh_askpass: exec(/usr/libexec/ssh-askpass): No such file or directory
Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Please note

• Error not reproducible in gnome-terminal (external)
• From global config: "terminal.integrated.shell.linux": "/bin/bash"
• Error not reproducible in integrated terminal (at least I get a prompt there to input my passphrase for my SSH key)
• SSH key is unlocked, so if I run git pull from gnome-terminal (external), I do not need to enter the passphrase
• In the integrated terminal I get asked for the passphrase for each command, so VS Code obviously cannot access the unlocked SSH keys (maybe because of the sandbox? I don't know if this can even be addressed...)
• In the integrated terminal, I do not have access to the commands ssh-add or similar. I thought I could just add the SSH key in the terminal to unlock it at least in the sandbox, but to no avail

Expected behaviour

• I expect the same behaviour as in the .deb release where I do not need to unlock the keys and it "just works" out of the box

VS Code Info

VS Code version: Code 1.20.1 (f88bbf9137d24d36d968ea6b2911786bfe103002, 2018-02-13T15:31:21.019Z)
OS version: Debian Stretch (Kernel: Linux x64 4.9.0-5-amd64)

Hi,

Global menu is not supported in kde plasma (it is supported on the non-flatpak version)

I think it could be easily changed by adding those permissions :

    "--filesystem=xdg-config/kdeglobals:ro",
    "--talk-name=com.canonical.AppMenu.Registrar",
    "--talk-name=com.canonical.AppMenu.Registrar.*"

It would be much more reliable to use tarball for extra data, as it has reliable URL scheme pointing to specific versions.

https://vscode-update.azurewebsites.net/1.18.1/linux-x64/stable

There is also a tarball for i686, so we could support both arches.

I use VSCode as an IDE mostly for C++, LaTeX and Rust. In the current form (where it hides system's /usr) it is completely unusable for me (except for Rust which is installed in my home dir). I've noticed that system /usr is mounted as /var/run/host/usr, so I'm wondering if there is a way to use binaries, include files and libs from there or that's not possible? I do realize that would be slightly breaking the sandbox, but those files are read-only anyway.

Hi there is a New update 1.20.1

For signing git commits, git uses GnuPG as an external program, defaulting to gpg. That binary is provided in the container, the problem with it is, it cannot use the gpg-agent as provided by Seahorse etc. and bails out on needing to supply a passphrase without a terminal.

The gpg program name can be overridden to gpg2 in git configuration, but this binary is not present in the container. Neither, I believe, the agent socket is forwarded from the desktop.

Freshly installed on Fedora 29, VS Code is not launching. Tried:

• GUI shortcut
• flatpak run com.visualstudio.code
• flatpak run --command=/app/extra/vscode/code com.visualstudio.code
• /var/lib/flatpak/exports/bin/com.visualstudio.code

The resulting error:
env: ‘/app/extra/vscode/bin/code’: No such file or directory

(or bwrap: execvp /app/extra/vscode/code: No such file or directory when using the third option above)

How can I get it to run? How can I help debug this?

To facilitate working with git over ssh, it would be nice if the sandbox had access to the ssh-agent socket from the user session. flatpak/flatpak#1438 says this is feasible with manual override options of flatpak run, but it would be great if the app had it out of the box.

Python extension for Visual Studio Code can not install pylint:

sh-4.3$ "python" -m pip install -U pylint
You are using pip version 7.1.0, however version 9.0.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
...
Exception:
...
OSError: [Errno 30] Read-only file system: '/usr/lib/python2.7/site-packages/backports.functools_lru_cache-1.4.dist-info'

Steps to reproduce:

1. fresh install com.visualstudio.code
2. install python extension
3. open python project, appears notification bar with message "Linter pylint is not installed"
4. click in "Install pylint" button

PS. And how about python3 support?

It prompts this and 1.30.1 is available.

When I tried to tun update via flatpak, there is no update available.

In the About menu, it also seems the old version:

Version: 1.30.0
Commit: c6e592b2b5770e40a98cb9c2715a8ef89aec3d74
Date: 2018-12-11T22:21:33.585Z
Electron: 2.0.12
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
OS: Linux x64 4.15.0-42-generic

On Fedora, this is where the credential helper is stored. Without it, I have to enter username and password ever time. GNOME keyring integration does not seem to exist in Fedora?!

Alternatively: know a better solution?

I see flathub has org.freedesktop.Sdk.Extension.golang i've installed it. Is there a way to make this flatpak utilize it?

https://dev.to/satimewallin/go--mess-with-flatpakvscode-ja6 Here is something someone has done to get around this. Its definitely not ideal though :(

As part of the Unity Hub Flatpak, Visual Studio Code needs to be able to handle C# code via Omnisharp. This has gotten me a bit stuck, as Omnisharp (as well as some other VS Code extensions) wants the dotnet SDK binary to be directly in $PATH, but it's in /usr/lib/sdk/dotnet/bin. You could technically use an override to add it to the PATH, but having this be required just to use Untiy Hub doesn't seem overly user friendly.

In fact, this is really a general problem. Flatpak intentionally doesn't add SDK extensions to the PATH to avoid conflicts, but sometimes we just need it there.

Now comes the idea: include a "Flatpak SDK Extension PATH Manager" (name of course not final) extension as part of the default installation. This extension would have a check box for every installed SDK extension, and the user could mark the boxes for the SDK extensions they want to be in their PATH. Whenever VS Code is started, the "Flatpak SDK Path Manager" VS Code extension would go through all the selected SDK extensions and update the VS Code environment with the SDK extensions' enable.sh environment.

This would avoid the potential conflicts (as the user is still in charge of deciding what goes in the PATH and what doesn't), but it would also make it far more user-friendly to be able to add whatever is needed to the default PATH without having to mess with overrides and the Flatpak CLI.

The release information in the .appdata.xml file, visible via Flathub application metadata in GNOME Software tool and elsewhere, still lists version 1.18.0, even though commits have been made that update the downloaded installables to 1.19.1.

The remote icon in the appdata needs 64x64 and 128x128px icons to show up in GNOME Software properly, or we could just import the proper icon since we're now much more OK with the trademark implications.

I receive update today and notice that npm is not bundle buildin like the before build. i don't mind if i need to use nodejs preinstall on my OS. But it really easy to have a npm command inside buildin vscode terminal.

Thank you!