Hmbown/CodeWhale · error · anyhow::Error

xAI OAuth lifecycle lock changed repeatedly while opening

Error message

xAI OAuth lifecycle lock changed repeatedly while opening

What it means

Thrown on Windows when the xAI OAuth lifecycle lock open loop gives up: the code repeatedly tries to create/open the empty lock file, and if the file keeps changing state between attempts (created, secured, then observed different), it bails after exhausting the loop rather than risking operating on a lock it does not own. It is contention/interference detection, not corruption of credentials.

Source

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

            let secured = (|| -> Result<()> {
                validate_windows_file_shape(&file, &path)?;
                secure_windows_owner_only_handle(&file, false)
                    .context("securing a new xAI OAuth lifecycle lock")?;
                validate_owned_file_handle(&file, &path)?;
                Ok(())
            })();
            if let Err(error) = secured {
                let cleanup = mark_windows_file_handle_for_deletion(&file);
                return match cleanup {
                    Ok(()) => Err(error),
                    Err(cleanup) => Err(error).context(format!(
                        "also failed to delete the empty lifecycle lock: {cleanup:#}"
                    )),
                };
            }
            return Ok(file);
        }
        bail!("xAI OAuth lifecycle lock changed repeatedly while opening")
    }

    fn write_owned_file(&self, name: &str, bytes: &[u8], allow_replace: bool) -> Result<()> {
        let path = self.directory.join(name);
        if let Some(existing) = self.open_owned_file_for_read(name)? {
            anyhow::ensure!(
                allow_replace,
                "refusing to replace an existing xAI OAuth generation"
            );
            drop(existing);
        }
        let mut temporary = tempfile::NamedTempFile::new_in(&self.directory)
            .context("creating private xAI OAuth temporary file")?;
        let temporary_path = temporary.path().to_path_buf();
        let security_handle =
            reopen_windows_file_for_owner_security(temporary.as_file(), &temporary_path)?;
        secure_windows_owner_only_handle(&security_handle, false)
            .context("securing a new xAI OAuth temporary file before writing credentials")?;

View on GitHub (pinned to 0c42157ee5)

Solutions

Retry the operation once contention subsides — this error is transient by nature
Serialize credential lifecycle operations so only one process refreshes at a time (lock in your job scheduler)
Exclude the credentials directory from antivirus real-time scanning and file sync, and give parallel jobs separate CODEWHALE_HOME roots

Defensive patterns

Strategy: retry

Try / catch

const MAX_ATTEMPTS: usize = 3;
for attempt in 1..=MAX_ATTEMPTS {
    match run_oauth_lifecycle_op() {
        Ok(v) => break Ok(v),
        Err(err) if err.to_string().contains("changed repeatedly") && attempt < MAX_ATTEMPTS => {
            tokio::time::sleep(std::time::Duration::from_millis(250 * attempt as u64)).await;
            continue;
        }
        Err(err) => break Err(err),
    }
}

Prevention

Serialize login/refresh jobs with an outer scheduler lock so lock contention cannot happen
Exclude the credentials directory from antivirus real-time scanning and file sync on Windows
Give each concurrent job its own CODEWHALE_HOME

When it happens

Trigger: Two or more codewhale processes on Windows performing xAI OAuth lifecycle operations (login/refresh) against the same CODEWHALE_HOME at the same time; antivirus, indexing, or sync software repeatedly touching the empty lock file in the credentials directory during the open window.

Common situations: Scheduled task and interactive session both refreshing credentials; CI agents sharing a home directory; aggressive real-time scanners recreating/locking small files.

Related errors

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