vscode: Can't start selfhost build
The terminal process "/bin/zsh '-c', 'yarn run watch-extensionsd'" failed to launch (exit code: 127).
I get this when running the build task from VSCode insiders (Cmd+Shift+B
).
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 3
- Comments: 23 (20 by maintainers)
Commits related to this issue
- Use shell environment based on setting Fixes #123072 — committed to microsoft/vscode by Tyriar 3 years ago
- Include useShellEnvironment in shell dto Part of #123072 — committed to microsoft/vscode by Tyriar 3 years ago
I can confirm it’s working also, thanks!
Should be fixed now after a debug session with @joaomoreno
Here’s my plan for this:
terminal.integrated.inheritEnv
, keep the default astrue
which will use the patched environment andfalse
we will use the unpatched environment (instead of the solution which had a bunch of issues before).IShellLaunchConfig.inheritEnv?: boolean
which will let tasks override whatever the setting is since they could break otherwise.$PATH
may be missing in regular terminals whenterminal.integrated.inheritEnv
is set tofalse
. This will be considered by design and it will be up to the user to run their terminal as a login shell if that’s desired, I’ll explain this in theterminal.integrated.inheritEnv
config description.@jasonwilliams I believe that build didn’t contain the fix yet. We just released another Insiders which contains the fix, my issue is gone:
@jasonwilliams do you have any terminal settings set?
I still get this issue in today’s Insiders. Toggling
terminal.integrated.inheritEnv
makes no difference at all. 😢Looks like a regression from the removal of shell env in renderer and/or shared process, does not reproduce when running from a terminal.