User-defined PATH no longer sourced in remote ssh session after 1.87.1 release

[JtMotoX]

Does this issue occur when all extensions are disabled?: Yes

• VS Code Version: 1.87.1
• OS Version (local): Windows 11
• OS Version (remote ssh): AlmaLinux 8.9

Steps to Reproduce:

Server Steps (Linux):

1. Make sure git is not installed
2. Install git in a non-standard path (git installed via nix in my case)
3. Update your profile file (.zshrc, .bashrc, .bash_profile, etc..) and update your PATH to include the non-standard directory where you installed git.
4. Clone any git repo

Client Steps (Windows):

1. Install code 1.87.1
2. Remote SSH to the linux server
3. Open the git repo you cloned earlier
4. VSC will not detect that it is a git repo and complains that git is not installed.

I have not run into this issue until updating to 1.87.1

[lszomoru]

Could you please share the contents of the git output window?

[JtMotoX]

2024-03-20 17:56:43.766 [info] Log level: Info
2024-03-20 17:56:43.766 [info] Validating found git in: "git"
2024-03-20 17:56:43.766 [warning] Unable to find git. Error: spawn git ENOENT
2024-03-20 17:56:43.766 [warning] Git installation not found.

[JtMotoX]

I finally found the issue. My custom systemd service script was executing the code serve-web command in a non-interactive shell (without login). I added the -l flag for a non-interactive login shell.

Before:

COMMAND="${CODE_CLI} serve-web . . ."
${COMMAND}

After:

COMMAND="${CODE_CLI} serve-web . . ."
${SHELL} -l -c "${COMMAND}"

Now that the process is "logging in" and loading my zsh profile, my ~/nix-profile/bin directory is now included in my PATH and all my user-defined environment variables are loaded.