atuinsh/atuin · error

unknown error

Error message

unknown error

What it means

Wildcard arm of the status match in the auth-module change_password: the PATCH /account/password returned any status other than 200/401/403, so no specific diagnosis exists. A deliberately low-information sentinel; the concrete HTTP status is discarded by the match.

Source

Thrown at crates/atuin-client/src/auth.rs:211

        let resp = client
            .patch(url)
            .json(&ChangePasswordRequest {
                current_password: current_password.to_string(),
                new_password: new_password.to_string(),
            })
            .send()
            .await?;

        match resp.status().as_u16() {
            200 => Ok(MutateResponse::Success),
            401 => {
                bail!("current password is incorrect");
            }
            403 => {
                bail!("invalid login details");
            }
            _ => {
                bail!("unknown error");
            }
        }
    }

    async fn delete_account(
        &self,
        password: &str,
        _totp_code: Option<&str>,
    ) -> Result<MutateResponse> {
        let client = self.authenticated_client()?;
        let url = self.address.append(["account"])?;

        let resp =
            client.delete(url).json(&serde_json::json!({ "password": password })).send().await?;

        match resp.status().as_u16() {
            200 => Ok(MutateResponse::Success),
            401 => {

View on GitHub (pinned to c0c717ab04)

Solutions

1. Retry the password change; transient server errors land here
2. Inspect network traffic or server logs to recover the actual status code
3. Check https://status.atuin.sh if the failure repeats

When it happens

Trigger: Thrown at crates/atuin-client/src/auth.rs:211 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of atuinsh/atuin@c0c717ab04 (2026-09-12). Data as JSON: /api/errors/87e625ad0e4dd5f8. Report an issue: GitHub.