Skip to main content

Module error

Module error 

Source
Expand description

The two error layers a Plexus client sees, kept apart by type.

The wire has two independent failure modes and conflating them is the bug this split exists to prevent:

LayerMeaningType
transportthe connection/HTTP call failed; nothing was said about the requestTransportError
remotethe server answered, and the answer is an error frame: the call failed, typedClientError::Remote (RemoteError)

Neither is the activation saying no. That is an err item — data, the Err half of a Result<T, E> item — and it reaches the caller as a value, never as a ClientError (RETURNS-1 decision 8). The one rule for a receiver: ? is the call failing; a match on the item is the activation’s answer.

match answer? {                       // ? = the call failed
    Ok(n) => show(n),                 // the activation's yes
    Err(why) => missing(&why),        // the activation's no
}

Structs§

TransportError
A failure of the transport itself — the request never got an answer, or the answer was unintelligible.

Enums§

ClientError
Everything that can go wrong on a typed client call — the call failing, never the activation saying no (that is an err item).
NameRefusal
Why an instance name cannot reach its instance (RETURNS-46): the service routes <parent>.<name>.<method> by name’s segment — a static child before the dynamic one — and refuses a path whose segments are not [a-z][a-z0-9_]* (plexus-auth-core’s MethodPath). A name that is a method of the parent is the instance: the service takes the first segment after the parent as a child, never as the parent’s method.
TransportErrorKind
What kind of transport failure occurred.