zed-industries/zed · error

Failed to run command: {command:?}: output: {}

Error message

Failed to run command: {command:?}: output: {}

What it means

In transport.rs run_cmd: a local command (used while building the remote server from source) exited unsuccessfully; the error embeds the command and its captured output. It fails the remote-server build pipeline step.

Source

Thrown at crates/remote/src/transport.rs:285

        std::env::var("ZED_BUILD_REMOTE_SERVER").unwrap_or("nocompress".into());

    if let "never" = &*build_remote_server {
        return Ok(None);
    } else if let "false" | "no" | "off" | "0" = &*build_remote_server {
        if binary_exists_on_server {
            return Ok(None);
        }
        log::warn!("ZED_BUILD_REMOTE_SERVER is disabled, but no server binary exists on the server")
    }

    async fn run_cmd(command: &mut Command) -> Result<()> {
        let output = command
            .kill_on_drop(true)
            .stdout(Stdio::inherit())
            .stderr(Stdio::inherit())
            .output()
            .await?;
        anyhow::ensure!(
            output.status.success(),
            "Failed to run command: {command:?}: output: {}",
            String::from_utf8_lossy(&output.stderr)
        );
        Ok(())
    }

    let use_musl = !build_remote_server.contains("nomusl");
    let triple = format!(
        "{}-{}",
        platform.arch,
        match platform.os {
            RemoteOs::Linux =>
                if use_musl {
                    "unknown-linux-musl"
                } else {
                    "unknown-linux-gnu"
                },

View on GitHub (pinned to f4178619ac)

Solutions

1. Inspect the included output for the build failure
2. Ensure build tools (cargo/rustc) are installed and up to date
3. Set ZED_BUILD_REMOTE_SERVER=never as a workaround

When it happens

Trigger: Thrown at crates/remote/src/transport.rs:285 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of zed-industries/zed@f4178619ac (2026-08-20). Data as JSON: /api/errors/7fb9bcabfdfac3b4. Report an issue: GitHub.