tinyhumansai/openhuman · error
resolved node bin missing: {} — install appears corrupted
Error message
resolved node bin missing: {} — install appears corrupted What it means
build_resolved assembled the platform-specific executable names (node/npm[.exe]) inside the resolved bin directory and the node binary is not a regular file. The install directory exists but its contents are incomplete — a corrupted, truncated or tampered managed install.
Source
Thrown at src/openhuman/runtime/node/bootstrap.rs:301
if cfg!(windows) {
install_dir.to_path_buf()
} else {
install_dir.join("bin")
}
}
/// Build a [`ResolvedNode`] from a bin directory by filling in the
/// platform-specific executable names.
fn build_resolved(bin_dir: PathBuf, version: String, source: NodeSource) -> Result<ResolvedNode> {
let (node_name, npm_name) = if cfg!(windows) {
("node.exe", "npm.cmd")
} else {
("node", "npm")
};
let node_bin = bin_dir.join(node_name);
let npm_bin = bin_dir.join(npm_name);
if !node_bin.is_file() {
bail!(
"resolved node bin missing: {} — install appears corrupted",
node_bin.display()
);
}
if !npm_bin.exists() {
tracing::warn!(
npm_bin = %npm_bin.display(),
"[node_runtime::bootstrap] npm launcher missing; npm_exec tool will fail until reinstall"
);
}
Ok(ResolvedNode {
bin_dir,
node_bin,
npm_bin,
version,
source,
})
}View on GitHub (pinned to 7491200858)
Solutions
- Delete the managed Node install directory (under the workspace runtime cache) so the next resolve() re-downloads a fresh distribution
- Check disk space and antivirus quarantine that may have removed the binary
Defensive patterns
Strategy: retry
When it happens
Trigger: Thrown at src/openhuman/runtime/node/bootstrap.rs:301 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of tinyhumansai/openhuman@7491200858 (2026-08-17).
Data as JSON: /api/errors/ee531afbce190831.
Report an issue: GitHub.