vectordotdev/vector · error

Failed to write

Error message

Failed to write {}: {}

What it means

After computing the new contents in memory, update_vector_version writes them back with fs::write. This error wraps any write failure — typically permission denied, read-only file/checkout, or disk full — and aborts the release preparation step for that file.

Solutions

1. Make the file writable (`chmod u+w <file>`), or fix ownership (`sudo chown $(whoami) <file>`).
2. Ensure the repo checkout is writable (don't run against a read-only mount; re-clone if needed).
3. Free disk space / raise quota (`df -h`) and re-run `vdev release prepare`.

Example fix

// before
-r--r--r-- Cargo.toml   # read-only -> write fails
// after
chmod u+w Cargo.toml && vdev release prepare

let meta = std::fs::metadata(file_path)?;
if meta.permissions().readonly() {
    panic!("{file_path:?} is read-only; make it writable before release prepare");
}

match std::fs::write(file_path, contents) {
    Ok(_) => /* proceed */,
    Err(e) => eprintln!("make file writable / free disk space: {e}"),
}

When it happens

Trigger: Prepare::run reaches the write-back of a bumped version file while the file is read-only, owned by another user, the checkout is read-only, or the filesystem is full.

Common situations: CI checkouts mounted read-only; files made read-only by `chmod 444`; running vdev as a non-owner user; disk quota exceeded on the build machine.

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

• Failed to read
• Could not find version
• Failed to bind to listener socket at path
• Failed to create output dir
• Failed to create output dir(s)

AI-assisted analysis of vectordotdev/vector@bdb87aeaa4 (2026-09-16). Data as JSON: /api/errors/308c7f09ccef789e. Report an issue: GitHub.

Appendix: source

Thrown at vdev/src/commands/release/prepare.rs:197

        let latest_version = &self.latest_vector_version;
        let new_version = &self.new_vector_version;
        let old_version_str = format!("{}.{}", latest_version.major, latest_version.minor);
        let new_version_str = format!("{}.{}", new_version.major, new_version.minor);

        if !contents.contains(&old_version_str) {
            return Err(anyhow!(
                "Could not find version {} to update in {}",
                latest_version,
                file_path.display()
            ));
        }

        let updated_contents =
            contents.replace(&latest_version.to_string(), &new_version.to_string());
        let updated_contents = updated_contents.replace(&old_version_str, &new_version_str);

        fs::write(file_path, updated_contents)
            .map_err(|e| anyhow!("Failed to write {}: {}", file_path.display(), e))?;

        Ok(())
    }

    /// Final step. Create a release prep PR against the release branch.
    fn open_release_pr(&self) -> Result<()> {
        debug!("open_release_pr");
        git::push()?;

        let new_vector_version = &self.new_vector_version;
        let pr_title = format!("chore(releasing): prepare v{new_vector_version} release");
        let pr_body = format!("This PR prepares the release for Vector v{new_vector_version}");
        let gh_status = Command::new("gh")
            .arg("pr")
            .arg("create")
            .arg("--draft")
            .arg("--base")
            .arg(self.release_branch.as_str())

View on GitHub (pinned to bdb87aeaa4)