Hmbown/CodeWhale · error · anyhow::Error

atomically replacing xAI OAuth credentials

Error message

atomically replacing xAI OAuth credentials

What it means

Wrapping context in the Windows persistence path for xAI OAuth credentials: tempfile::persist failed to atomically replace the credential file at its final path with the freshly written temporary file. The error is wrapped and routed through cleanup_windows_secret_after_error to scrub the temp secret before propagating.

Source

Thrown at crates/config/src/xai_credentials.rs:996

            temporary
                .as_file()
                .sync_all()
                .context("syncing xAI OAuth temporary file")?;
            Ok(())
        })();
        if let Err(error) = write_result {
            return Err(cleanup_windows_secret_after_error(
                &security_handle,
                error,
                "temporary file",
            ));
        }
        let persisted = if allow_replace {
            match temporary.persist(&path) {
                Ok(file) => file,
                Err(error) => {
                    let tempfile::PersistError { error, file } = error;
                    let persistence_error = anyhow::Error::new(error)
                        .context("atomically replacing xAI OAuth credentials");
                    let error = cleanup_windows_secret_after_error(
                        &security_handle,
                        persistence_error,
                        "temporary file",
                    );
                    drop(file);
                    return Err(error);
                }
            }
        } else {
            match temporary.persist_noclobber(&path) {
                Ok(file) => file,
                Err(error) => {
                    let tempfile::PersistError { error, file } = error;
                    let persistence_error = anyhow::Error::new(error)
                        .context("installing a new xAI OAuth generation without replacement");
                    let error = cleanup_windows_secret_after_error(

View on GitHub (pinned to 0c42157ee5)

Solutions

1. Retry the credential write; transient locks (AV scanners, sync clients) often clear on retry.
2. Ensure no other process holds the credential file open with incompatible sharing flags.
3. Check ACLs/permissions on the credentials directory allow replacement.

When it happens

Trigger: Thrown at crates/config/src/xai_credentials.rs:996 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of Hmbown/CodeWhale@0c42157ee5 (2026-08-20). Data as JSON: /api/errors/c4e9e3b2db70a5f3. Report an issue: GitHub.