Struct UpstreamVoucherRejected 

#[non_exhaustive]
pub struct UpstreamVoucherRejected {
    pub reason: VoucherRejectReason,
    pub bundle: Option<WatermarkBundle>,
    pub proof_generation: Option<u64>,
}

Typed sentinel for the upstream rejecting a voucher we presented mid-stream (#857) — e.g. a stale nonce (#852), deposit exhaustion, or a wrong-channel mismatch. This is OUR payment-side fault, not the provider’s, so the pull orchestrator downcast_refs it to skip the candidate WITHOUT recording a reputation observation (mirroring the buyer channel-open-failure arm). Named with the Upstream prefix to disambiguate from the protocol-level StreamError::VoucherRejected reason enum, whose reason it carries verbatim (the Copy VoucherRejectReason, not a lossy stringification) so a future caller can branch on retry-vs-top-up-vs-abandon without re-parsing a message. Display keeps the stable voucher rejected text for logs.

bundle mirrors the wire WatermarkBundle verbatim (issue #1481): Some only for a watermark-gated reason (VoucherRejectReason::is_watermark_gated), and only when the node verified the rejected voucher recovered to the pool capability’s pinned signer before attaching it. A caller that sees Some can self-heal when the bundle advances its ledger — reseed to the bundle’s watermark (crate::ledger::Cumulative::from) and resume from bytes_delivered — or, on Underpaid, rebase down to it, rather than treating the rejection as terminal. SpendingCapExhausted with bundle: None means there is no signer-verified watermark to resume from (or, more commonly, that a wallet-less delegate simply has no local means to add deposit) — the caller must surface that to the app rather than loop. CapabilityExpired and PoolExhausted are never watermark-gated (no bundle is ever attached) and are always terminal — the fix is a fresh capability or an owner top-up, not a resync.

Fields (Non-exhaustive)

Non-exhaustive structs could have additional fields added in future. Therefore, non-exhaustive structs cannot be constructed in external crates using the traditional Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.

reason: VoucherRejectReason

Why the seller refused the voucher.

bundle: Option<WatermarkBundle>

The seller’s signer-verified watermark, when it sent one, so the buyer can resync its cumulative state and retry. None means there is nothing to resync from and the caller must surface the failure.

proof_generation: Option<u64>

The ledger generation the rejected voucher was signed under (StreamProof::Voucher), when the stream knows it. None for a rejected reveal, or a rejection read before this stream claimed anything; PoolLedger::rebase treats it as current.

Trait Implementations

impl Debug for UpstreamVoucherRejected

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

Formats the value using the given formatter.

impl Display for UpstreamVoucherRejected

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

Formats the value using the given formatter.

impl Error for UpstreamVoucherRejected

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.