What causes "Failed to write to '{}', No parent path" in sigoden/aichat?

Pass a path that includes a directory component, e.g. './foo.txt' instead of 'foo.txt'

sigoden/aichat · error · anyhow::Error

Failed to write to ' ', No parent path

Error message

Failed to write to '{}', No parent path

What it means

ensure_parent_exists validates that a path can be written: if the path itself doesn't exist, it needs a parent directory to create. Paths with no parent component (e.g. a bare relative filename like 'foo.txt' resolving to an empty parent, or a root-level path edge case) fail this check before any write is attempted.

Solutions

Pass a path that includes a directory component, e.g. './foo.txt' instead of 'foo.txt'
Create the parent directory yourself before calling
Check the path construction logic so the target file always sits inside an explicit directory

Example fix

// before
ensure_parent_exists(Path::new("config.yaml"))?
// after
ensure_parent_exists(Path::new("./config.yaml"))?

Defensive patterns

Strategy: validation

Validate before calling

fn writable(path: &Path) -> bool {
    path.exists() || path.parent().map(|p| !p.as_os_str().is_empty()).unwrap_or(false)
}

Try / catch

match ensure_parent_exists(path) {
    Ok(()) => write(path, data)?,
    Err(e) if e.to_string().contains("No parent path") => {
        let p = Path::new("./").join(path);
        ensure_parent_exists(&p)?; write(&p, data)?;
    }
    Err(e) => return Err(e),
}

Prevention

Always build target paths with an explicit directory component
Prefer PathBuf::from(".").join(name) over bare filenames
Normalize user-supplied paths before writing

When it happens

Trigger: Calling ensure_parent_exists (directly or via a config/file write path) with a Path that has no parent component and does not already exist.

Common situations: Passing a bare filename without a directory component where the code expects 'dir/file'; constructing paths from user input that strip the directory; unusual relative paths like './' mis-parsed.

Understand the failure class

Background: "failed to write file", "Could not save figure", "Error saving remote file" — file write failed: causes and fixes across languages and libraries — this error's family across 38 libraries.

Related errors

AI-assisted analysis of sigoden/aichat@82976d349a (2026-09-09). Data as JSON: /api/errors/eb8790ecdb1ecf55. Report an issue: GitHub.

Appendix: source

Thrown at src/config/mod.rs:2665

    #[cfg(unix)]
    {
        use std::os::unix::prelude::PermissionsExt;
        let perms = std::fs::Permissions::from_mode(0o600);
        std::fs::set_permissions(config_path, perms)?;
    }

    println!("✓ Saved the config file to '{}'.\n", config_path.display());

    Ok(())
}

pub(crate) fn ensure_parent_exists(path: &Path) -> Result<()> {
    if path.exists() {
        return Ok(());
    }
    let parent = path
        .parent()
        .ok_or_else(|| anyhow!("Failed to write to '{}', No parent path", path.display()))?;
    if !parent.exists() {
        create_dir_all(parent).with_context(|| {
            format!(
                "Failed to write to '{}', Cannot create parent directory",
                path.display()
            )
        })?;
    }
    Ok(())
}

fn read_env_value<T>(key: &str) -> Option<Option<T>>
where
    T: std::str::FromStr,
{
    let value = env::var(key).ok()?;
    let value = parse_value(&value).ok()?;
    Some(value)

View on GitHub (pinned to 82976d349a)