Extensions possibly don't inherit PATH/environment correctly?

gitpod-io / openvscode-server

Run upstream VS Code on a remote machine with access through a modern web browser from any device, anywhere.

https://www.gitpod.io/

MIT License

4.84k stars 423 forks source link

Extensions possibly don't inherit PATH/environment correctly? #545

Open colemickens opened 5 months ago

colemickens commented 5 months ago

Does this issue occur when all extensions are disabled?: n/a

VS Code Version: Version: 1.84.0
OS Version: nixos linux 6.6.8

Steps to Reproduce:

use openvscode-server with systemd
use nix-environment-selector and select a shell.nix that includes rust-analyzer
note that rust-analyzer can't find the binary, even if you tell it to look for rust-analyzer (aka in PATH)

this works in desktop vscodium.

colemickens commented 5 months ago

Oh, I left out the most interesting part, terminals launched after restarting seem to have inherited PATH though. I don't have rust-analyzer installed system wide, yet I can use it in a OVSCS Terminal after using nix-env-selector.

colemickens commented 5 months ago

I suspect this may have to do with how systemd is running/managing the process, since I'm running it as a service. When I run it by hand from the command line, things seem to work as expected.