sed: command not found shows up when opening gitbash terminal

[anthonykim1]

bash: basename: command not found
bash: uname: command not found
bash: sed: command not found
bash: sed: command not found
()
REDMOND+kanadig@kanadig-dev1 MINGW64 /c/GIT/projects/vscode-copilot-evaluation

basename and uname was from activate script. sed might be from shell integration script?

/cc @karthiknadig

[anthonykim1]

We do have references to sed in shell integration bash script:

vscode/src/vs/workbench/contrib/terminal/common/scripts/shellIntegration-bash.sh

Line 214 in 6711af1

builtin printf "\e]633;P;ContinuationPrompt=$(echo "$PS2" | sed 's/\x1b/\\\\x1b/g')\a"

and

vscode/src/vs/workbench/contrib/terminal/common/scripts/shellIntegration-bash.sh

Line 402 in 6711af1

__vsc_current_command="$(builtin history 1 | sed 's/ *[0-9]* *//')"

So maybe they are what is showing this. I haven't seen this come up in issues though, and has been there for either 15 month or 3years.

Maybe the bash version is just super old??

[xfornari]

Found that VSCODE_ENV_REPLACE variable is the responsible.
My situation:

• running VS Code on Windows
• using Git bash as terminal
• default terminal profile: Git bash
• Python setting: Env file = ${workspaceFolder}/.env

There is no .env in my workspace, and still VSCODE_ENV_REPLACE contains the PATH defined from the Windows environment variables, with the Windows format.

Result: proper PATH from .bashrc , which is loaded by shellIntegration-bash.sh, is immediately destroyed by if [ -n "${VSCODE_ENV_REPLACE:-}" ]; then ... in that script. The shell PATH has now a kind of Windows format PATH=C\x3a\Program Files\dotnet;...`, which is invalid.

I couldn't find who set VSCODE_ENV_REPLACE.
My current workaround is to edit shellIntegration-bash.sh and add builtin unset VSCODE_ENV_REPLACE

[anthonykim1]

@xfornari That sounds different.

Closing since not reproducible for this sed issue

[anthonykim1]

We'd still want this as for alphine. Maybe could just disable feature as fallback?

[xfornari]

@anthonykim1 : it is not only a sed issue.

The main issue I have is: VSCODE_ENV_REPLACE is set even if I don't have the .env file, and could find who set it.
Consequences:
a. shellIntegration-bash.sh loads my .bashrc
b. it considers VSCODE_ENV_REPLACE
c. unexpected content of VSCODE_ENV_REPLACE are Windows paths
d. the sed script uses therefore improper data and the result is an invalid PATH

as a result, I got the error message "basename" and "sed" not found from the bash function which is used to update PS1 in the git context.

[anthonykim1]

@xfornari Interesting..
What version of VS Code , and Python extension are you running?
Also if you are using remote?

Also run command workbench.action.terminal.showEnvironmentContributions to see who is replacing your unwanted variable.
Maybe also try adding "python.experiments.optOutFrom": ["pythonTerminalEnvVarActivation"] into your settings.json if its Python extension who is modifying your PATH.