tinyhumansai/openhuman · error

venv created but interpreter missing at {}

Error message

venv created but interpreter missing at {}

What it means

The spaCy venv creation command succeeded but the venv's python binary is missing afterwards — silent creation failure (disk, permissions, antivirus) or a broken venv layout on this platform.

Source

Thrown at src/openhuman/runtime/python_server/spacy.rs:124

        .resolve()
        .await
        .context("resolving base python for runtime python server spaCy venv")?;
    log::debug!(
        "[runtime_python_server::spacy] base python resolved version={} bin={}",
        base.version,
        base.python_bin.display()
    );

    run_step(
        &base.python_bin,
        &["-m", "venv", &venv_dir.to_string_lossy()],
        VENV_TIMEOUT,
        "create venv",
    )
    .await?;

    if !venv_python.exists() {
        bail!(
            "venv created but interpreter missing at {}",
            venv_python.display()
        );
    }

    run_step(
        &venv_python,
        &spacy_pip_install_args(),
        PIP_TIMEOUT,
        "pip install spacy",
    )
    .await?;

    run_step(
        &venv_python,
        &["-m", "spacy", "download", SPACY_MODEL],
        PIP_TIMEOUT,
        "spacy download model",

View on GitHub (pinned to 7491200858)

Solutions

1. Delete the spaCy venv directory so provisioning re-runs
2. Check disk space, permissions and antivirus interference on the venv path

When it happens

Trigger: Thrown at src/openhuman/runtime/python_server/spacy.rs:124 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/ebedff4b72327001. Report an issue: GitHub.