zed-industries/zed · error

unexpected resolved path from the path resolution script: {p

Error message

unexpected resolved path from the path resolution script: {path:?}

What it means

A result line from the path resolution script carried a well-formed status pair but a path that is not absolute, violating the script's strict protocol. Indicates script corruption or a helper version mismatch.

Source

Thrown at crates/sandbox/src/windows_wsl.rs:1164

        .into_iter()
        .map(|line| {
            let mut parts = line.splitn(3, ' ');
            let (Some(translate), Some(exists), Some(path)) =
                (parts.next(), parts.next(), parts.next())
            else {
                bail!("malformed line from the path resolution script: {line:?}");
            };
            let used_fallback = match translate {
                "ok" => false,
                "fallback" => true,
                _ => bail!("malformed line from the path resolution script: {line:?}"),
            };
            let exists = match exists {
                "ok" => true,
                "missing" => false,
                _ => bail!("malformed line from the path resolution script: {line:?}"),
            };
            ensure!(
                path.starts_with('/'),
                "unexpected resolved path from the path resolution script: {path:?}"
            );
            Ok(ResolvedPath {
                path: path.to_string(),
                used_fallback,
                exists,
            })
        })
        .collect()
}

/// `CREATE_NO_WINDOW` process creation flag. `wsl.exe` is a console-subsystem
/// binary, so spawning it from a GUI process without this flag flashes a
/// console window. Defined locally because this crate doesn't depend on
/// `util` (whose command helpers normally take care of this).
const CREATE_NO_WINDOW: u32 = 0x0800_0000;

View on GitHub (pinned to f4178619ac)

Solutions

1. Retry the resolution to rule out transient output corruption
2. Re-provision the helper script so its output matches the expected protocol

When it happens

Trigger: Thrown at crates/sandbox/src/windows_wsl.rs:1164 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/3fabb6d6de8c5af3. Report an issue: GitHub.