Enum ApiError 

pub enum ApiError {
    Cloudflare {
        detail: String,
    },
    BrowserGone {
        detail: String,
    },
    AuthExpired,
    StaleBuild {
        wanted: Option<String>,
    },
    Api {
        status: u16,
        message: String,
    },
    InvalidRequest(String),
    Other(Error),
}

Why a /kr-api/ call did not produce a usable answer.

ApiError::Cloudflare and ApiError::BrowserGone both relaunch against the same profile; ApiError::AuthExpired must never touch it, or a transient failure destroys a real login.

Variants

Cloudflare

Bot mitigation. Relaunch against the same profile dir; never delete it.

Raised both by an API response that carries a Cloudflare fingerprint and by the page load itself being rejected. Both need the same remedy, so both must land here – a block during navigation reported as ApiError::Other would silently bypass the relaunch that is the only remedy for it.

Fields

detail: String

BrowserGone

The transport to Chrome died. The browser is broken, not the login it holds, so the remedy is the same relaunch as ApiError::Cloudflare.

Fields

detail: String

AuthExpired

The K-Plussa session is gone. Do not retry, do not touch the profile.

StaleBuild

X-K-Build-Number was absent or unparseable. Recoverable: the 409 that reports it carries the real value in its own k-ruoka-build header.

Despite K-Ruoka’s wording (“Client version is too old”), this does not mean they deployed: the header is presence-checked and must parse as a number, but the value is never compared. In practice this fires on a process’s first call, before the header has been learned.

Fields

wanted: Option<String>

Api

The API understood us and said no.

Fields

status: u16

message: String

InvalidRequest(String)

We rejected the request before sending it – a bad argument, not a K-Ruoka failure. Kept separate so the message cannot imply that K-Ruoka was asked and refused. It still reaches the caller as isError: true content like every other tool failure, deliberately: the model is meant to read it and try something else, which a JSON-RPC invalid_params does not guarantee.

Other(Error)

Trait Implementations

impl Debug for ApiError

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Display for ApiError

fn fmt(&self, __formatter: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Error for ApiError

fn source(&self) -> Option<&(dyn Error + 'static)>

Returns the lower-level source of this error, if any.

fn description(&self) -> &str

👎Deprecated since 1.42.0:

use the Display impl or to_string()

fn cause(&self) -> Option<&dyn Error>

👎Deprecated since 1.33.0:

replaced by Error::source, which can support downcasting

fn provide<'a>(&'a self, request: &mut Request<'a>)

🔬This is a nightly-only experimental API. (error_generic_member_access)

Provides type-based access to context intended for error reports.

impl From<Error> for ApiError

fn from(source: Error) -> Self

Converts to this type from the input type.