From e5bb3bfd35c1cf8c2e44e3172071f471adeb83ab Mon Sep 17 00:00:00 2001 From: "GustavoWidman (laptop-mac)" Date: Fri, 10 Oct 2025 23:46:20 -0300 Subject: [PATCH] fix: regression on SSH remotes not running NuShell NuShell does not support `uname -sm`, so invoke `sh -c "uname -sm"` instead which will also work under nushell. See nushell/nushell#12570 for the choice quote: "being posix/bash compliant is a non-goal". This was already patched and merged a few months ago in #25613, which fixed the original issue (#21005) but there seems to have been a regression of sorts, maybe when migrating/refactoring something. --- crates/remote/src/transport/ssh.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/crates/remote/src/transport/ssh.rs b/crates/remote/src/transport/ssh.rs index 909ff93169a8a9..c2f49746141afe 100644 --- a/crates/remote/src/transport/ssh.rs +++ b/crates/remote/src/transport/ssh.rs @@ -789,7 +789,7 @@ impl SshSocket { } async fn platform(&self) -> Result { - let uname = self.run_command("uname", &["-sm"]).await?; + let uname = self.run_command("sh", &["-c", "uname -sm"]).await?; let Some((os, arch)) = uname.split_once(" ") else { anyhow::bail!("unknown uname: {uname:?}") };