Enum Error 

#[non_exhaustive]
pub enum Error {
    Config(String),
    Transport(Error),
    Unauthorized {
        message: String,
    },
    PayloadTooLarge {
        message: String,
    },
    Overloaded {
        message: String,
        retry_after: Option<Duration>,
    },
    BlobsStillMissing {
        missing: Vec<MissingBlob>,
    },
    #[non_exhaustive]
    Server {
        status: u16,
        code: ErrorCode,
        message: String,
        detail: Vec<String>,
    },
    UnexpectedStatus {
        status: u16,
        body: String,
    },
    InvalidResponse {
        status: u16,
        reason: String,
    },
    MissingAsset {
        key: String,
    },
    BlobFetchFailed {
        key: String,
        source: BlobFetchError,
    },
    UnknownDigest {
        digest: Digest,
    },
    DigestMismatch {
        key: String,
        declared: Digest,
        actual: Digest,
    },
}

Non-exhaustive, like Error::Server’s fields: new failure modes and new server-supplied fields are not breaking changes, so a match needs a wildcard arm and a Server { .. } pattern a ...

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.

Config(String)

The client was built with a base URL or token it cannot use.

Transport(Error)

The request never completed: DNS, connect, TLS, timeout, or a body that could not be read to the end.

Unauthorized

401 — the bearer token is missing or wrong. The remedy is credentials, not payload, which is why it is not folded into Error::Server.

Fields

message: String

PayloadTooLarge

413 — the body exceeded the server’s MDCAST_MAX_UPLOAD_BYTES. Retrying the identical request is hopeless; the caller has to shrink or split it.

Fields

message: String

Overloaded

503 with code overloaded — every render slot stayed busy for the server’s whole queue wait. The request itself is fine: send it again after retry_after (the server’s Retry-After, when it sent one).

Fields

message: String

retry_after: Option<Duration>

BlobsStillMissing

A second 409 for the same render after the missing blobs were uploaded. The client retries exactly once — the same digests coming back means eviction is racing the retry or the server is misbehaving, and looping would only hide it.

Fields

missing: Vec<MissingBlob>

#[non_exhaustive]

Server

The server answered with its own ErrorResponse — the code, the message and any detail (sanitised engine diagnostics, sent only by a server with MDCAST_EXPOSE_DIAGNOSTICS on) are carried through verbatim.

Fields

Non-exhaustive enum variants could have additional fields added in future. Therefore, non-exhaustive enum variants cannot be constructed in external crates and cannot be matched against.

status: u16

code: ErrorCode

message: String

detail: Vec<String>

UnexpectedStatus

A status this protocol does not define, or one whose body is not an ErrorResponse (a proxy or load balancer answering instead of mdcast).

Fields

status: u16

body: String

InvalidResponse

The status was one the protocol defines, but its body did not decode.

Fields

status: u16

reason: String

MissingAsset

A manifest entry the bundle holds no bytes for. Caught locally: a 409 naming it would only tell the caller a digest it cannot resolve.

Fields

key: String

BlobFetchFailed

A digest-only bundle entry’s fetch closure failed to produce bytes at all, while satisfying an upload the server actually asked for. Never a silent skip — the retry would just 409 on the same digest again.

Fields

key: String

source: BlobFetchError

UnknownDigest

A digest asked for by hand (via crate::Client::upload) that nothing in the bundle hashes to.

Fields

digest: Digest

DigestMismatch

A caller-supplied manifest that disagrees with the bundle’s actual bytes. The upload would be rejected server-side anyway — the server re-hashes every byte — so it fails before the round trip. Also raised when a digest-only entry’s fetch succeeds but the bytes it returns hash to something other than the digest it was declared with.

Fields

key: String

declared: Digest

actual: Digest

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.