Enum BridgeError 

pub enum BridgeError {
    Unreadable(EnvelopeError),
    FeatureUnavailable {
        feature: Feature,
    },
    Unreachable {
        reason: String,
    },
    Close(String),
    NotReadable(LowerError),
    MethodNotBridged {
        method: String,
        downstream: ProtocolSide,
    },
}

Why a bridge could not carry an envelope.

Variants

Unreadable(EnvelopeError)

The envelope is not a JSON-RPC message, or a member has the wrong type.

FeatureUnavailable

The peers never settled on the same feature.

Fields

feature: Feature

The feature that was asked for.

Unreachable

The upstream peer could not be reached, or hung up.

Deliberately not carrying the peer’s own error envelope: a protocol refusal travels as a normal Err-free envelope, so reaching this arm means the message genuinely did not get through.

Fields

reason: String

What the transport reported.

Close(String)

Shutting the connection down failed.

NotReadable(LowerError)

The reply could not be expressed at the downstream client’s revision.

Not a transport failure and not the upstream’s refusal — the upstream answered, and the answer is in a dialect the client did not negotiate. Under a strict policy the bridge refuses rather than hand over something the client cannot read; the cause names the feature and the revision so the operator can tell a missing capability from a bug.

MethodNotBridged

The method is one this bridge’s cross-protocol codec has no rule for.

Distinct from FeatureUnavailable: FeatureUnavailable means the two peers share no feature for the method at all; MethodNotBridged means the bridge could in principle carry it (the codec for the relevant protocol pair exists) but the specific method is not modelled yet. The loop renders both as -32601 Method not found, but the operator needs to tell them apart: a FeatureUnavailable is a configuration gap, a MethodNotBridged is a follow-up commit.

Gated behind the a2a feature because the only bridge that surfaces it is a cross-protocol one, and the type it carries (ProtocolSide) is itself feature-gated. A default-features build has no cross-protocol bridge and therefore no way to produce this variant, so it is omitted from the enum rather than carrying a degenerate form.

Fields

method: String

The method the client called, by the wire name it sent.

downstream: ProtocolSide

The protocol side the call came in on.

Trait Implementations

impl Debug for BridgeError

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

Formats the value using the given formatter.

impl Display for BridgeError

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

Formats the value using the given formatter.

impl Error for BridgeError

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<A2aPeerError> for BridgeError

fn from(err: A2aPeerError) -> Self

Converts to this type from the input type.

impl From<BridgeError> for LoopError

fn from(source: BridgeError) -> Self

Converts to this type from the input type.

impl From<BridgeError> for UpstreamError

fn from(error: BridgeError) -> Self

Converts to this type from the input type.

impl From<EnvelopeError> for BridgeError

fn from(source: EnvelopeError) -> Self

Converts to this type from the input type.

impl From<LowerError> for BridgeError

fn from(source: LowerError) -> Self

Converts to this type from the input type.