Enum TrqlError 

pub enum TrqlError {
    Config(String),
    Transport {
        kind: TransportKind,
        detail: String,
    },
    Timeout {
        kind: TransportKind,
        waited_secs: u64,
    },
    Rejected {
        code: TrustTaskCode,
        retryable: bool,
        retry_after: Option<DateTime<Utc>>,
        message: Option<String>,
    },
    Contract(String),
    AnswerMismatch {
        field: &'static str,
        asked: String,
        answered: String,
    },
    ReferralNotClosed {
        origin: String,
        answered: String,
    },
    NoMatchingTransport {
        ours: Vec<TransportKind>,
        theirs: Vec<TransportKind>,
    },
}

Errors returned by crate::TrqlClient and crate::TrqlTransport implementations.

Variants

Config(String)

The client or transport was built with missing/invalid configuration.

Transport

The transport could not complete the exchange (connect, send, or receive failure). Retryable at the caller’s discretion.

Fields

kind: TransportKind

Which binding failed.

detail: String

What actually happened, named per failure (never a generic hint).

Timeout

No reply arrived within the transport’s configured reply window.

Fields

kind: TransportKind

Which binding timed out.

waited_secs: u64

How long the transport waited.

Rejected

The registry answered with a trust-task-error document.

Fields

code: TrustTaskCode

Machine-readable trust-task error code.

retryable: bool

Whether the registry marked the failure retryable.

retry_after: Option<DateTime<Utc>>

Earliest retry instant, when the registry supplied one.

message: Option<String>

Human-readable detail from the registry, if any.

Contract(String)

The peer’s reply violated the Trust Task contract: it didn’t parse, wasn’t correlated to the request, or carried an unexpected type. This is a bug on one side of the wire, not a transient condition — it is never worth retrying.

AnswerMismatch

The reply is correlated to our request but answers a different TRQP tuple than the one we asked about.

Correlation proves the reply belongs to our exchange; it says nothing about what the reply is an answer to. A registry that echoes a different entity_id/authority_id/action/resource has answered someone else’s question, and treating it as ours silently substitutes the subject of an authorization decision.

Fields

field: &'static str

Which tuple member disagreed.

asked: String

The value we sent on the request.

answered: String

The value the registry echoed back.

ReferralNotClosed

We followed a referral to this registry, and its answer does not claim the authority that referred us.

A TrustRegistry referral in a VTC’s DID document is a self-assertion — anyone may publish a document naming any registry. Authority flows registry → subject, so a referral is only closed when the registry answers for the DID we started from. Until then the referral has established where to ask and nothing about the answer.

Fields

origin: String

The DID whose document referred us here.

answered: String

The authority the registry actually answered for.

NoMatchingTransport

The registry advertises no transport this client also speaks.

Carries both sides’ sets so an operator can see what to enable rather than guess. Never a silent downgrade to a transport the registry did not advertise.

Fields

ours: Vec<TransportKind>

Transports this client can use (compiled in and offered).

theirs: Vec<TransportKind>

Transports the registry advertises in its DID document.

Implementations

impl TrqlError

pub fn is_retryable(&self) -> bool

Whether retrying the same query could plausibly succeed.

Contract violations and configuration errors are never retryable; a registry rejection is retryable only when the registry said so.

Trait Implementations

impl Debug for TrqlError

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

Formats the value using the given formatter.

impl Display for TrqlError

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

Formats the value using the given formatter.

impl Error for TrqlError

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.