Issue with running shell commands

[PierrunoYT]

Version / branch / commit

zero 0.5.0

OS and environment

Win 11 Powershell

Steps to reproduce

Im not sure

Expected behavior

It should not faild on commands

Actual behavior

It fails on multiple commands

Relevant logs, screenshots, or error messages

[Vasanthdev2004]

Triaged this. It is already fixed, and I want to record how I got there because my first theory was wrong.

I assumed this was PowerShell 5.1 rejecting &&, since stock Windows 11 ships 5.1 rather than 7 and a chained command trips our windows_powershell_version preflight. That theory does not survive contact with the dates:

• You filed against 0.5.0. At v0.5.0, shellExecutable() returned cmd.exe on Windows, and cmd.exe handles && fine.
• windows_powershell_version did not exist yet. It arrived with fix(windows): use PowerShell for command execution #804, merged four days after you filed.

So the PowerShell path could not have been involved, because Zero was not using PowerShell when you hit this.

What you were actually reporting is the same Windows shell problem as #454, which #804 closed by moving command execution to PowerShell. The coreutils half of the screenshot belongs to the #411 and #458 family.

Closing as a duplicate of #454 unless you still see it on current main, in which case please reopen with a version from after #804 and I will take another look.

One thing worth its own issue, which came out of digging into this: detectShellOutputIssueForRuntime recognises MSYS and WSL failure shapes but has nothing for Schannel credential errors, so those surface as a bare non-zero exit with no diagnosis. I will raise that separately rather than fold it in here.

[Vasanthdev2004]

Closing as a duplicate of #454, which #804 fixed by moving Windows command execution to PowerShell.

If you still hit this on a build from after #804, please reopen with the version and I will pick it back up. The Schannel gap I mentioned above is now tracked separately as #819.