Enum Error 

#[non_exhaustive]
pub enum Error {
    Transport(Error),
    Api {
        status_code: u16,
        message: String,
    },
    Serialization(Error),
    InvalidResponse(String),
    ResponseTooLarge {
        limit: usize,
    },
    NotCancellable,
    OperationFailed {
        id: Uuid,
        status_code: u16,
        err: Option<String>,
    },
    PreconditionFailed {
        resource: String,
    },
    NotFound {
        resource: String,
    },
    InvalidRequest(String),
    WebSocketProtocol(String),
    Timeout {
        after: Duration,
        request_fully_sent: bool,
    },
}

Errors returned by crate::Client and every resource method built on top of it.

#[non_exhaustive] because this crate expects to grow new failure modes as more of the Incus API surface is covered - matching exhaustively on this enum today would make every future variant addition a breaking change for downstream crates.

Variants (Non-exhaustive)

Non-exhaustive enums could have additional variants added in future. Therefore, when matching against variants of non-exhaustive enums, an extra wildcard arm must be added to account for any future variants.

Transport(Error)

Api

Fields

status_code: u16

message: String

Serialization(Error)

InvalidResponse(String)

ResponseTooLarge

Fields

limit: usize

NotCancellable

OperationFailed

Fields

id: Uuid

status_code: u16

err: Option<String>

PreconditionFailed

Fields

resource: String

NotFound

Fields

resource: String

InvalidRequest(String)

WebSocketProtocol(String)

A WebSocket-level failure from the events feature’s /1.0/events subscription that is not a plain socket I/O error (those still map to Transport) - a protocol violation, oversized frame, or similar. Kept separate from Transport so a caller can tell “the connection itself broke” apart from “the daemon sent something the WebSocket layer rejected” without string-matching.

Timeout

request_fully_sent tells a caller building retry logic whether the request had already been fully written to the daemon when the timeout fired: if true, a mutating call (create/update/delete) may have already been received and acted on server-side even though the caller only sees this timeout - retrying could duplicate the operation. If false, nothing was sent and a retry is safe. Incus operations are not inherently idempotent, so this distinction matters for anything more than a manual “try again and see.”

Fields

after: Duration

request_fully_sent: bool

Trait Implementations

impl Debug for Error

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

Formats the value using the given formatter.

impl Display for Error

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

Formats the value using the given formatter.

impl Error for Error

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 Error

fn from(source: Error) -> Self

Converts to this type from the input type.

impl From<Error> for Error

fn from(source: Error) -> Self

Converts to this type from the input type.