Struct PullStalled 

#[non_exhaustive]
pub struct PullStalled {
    pub after: Duration,
}

Typed sentinel for an upstream that went SILENT mid-stream — bytes were flowing, and then no byte of progress for the stall budget (#1134). Distinct from PullTimeout, which is a bound of OURS elapsing, and the distinction is load-bearing:

A whole-transfer deadline cannot tell “the provider is dead” from “this blob is big” or “this link is slow”, so PullTimeout must NOT tar the provider — it fires on perfectly healthy transfers. A stall deadline resets on every byte received, so it fires ONLY when a provider stops delivering while we wait. That IS evidence the peer is unreachable, and classify_pull_failure scores it as such in the local per-peer EWMA (ADR 008).

What the bound rests on

Two things, and it is worth being precise about both, because scoring a peer on a bound that does not hold is how an honest node’s local reputation gets unfairly defamed.

The non-empty-ChunkData invariant (#1088). With empty frames banned, “a frame arrived” and “bytes made progress” are the same statement, so a peer cannot hold the floor open with padding. The receive loop ([UpstreamPull::next_chunk]) has no independent progress check behind that floor: it is safe because no frame a peer can send makes zero progress, not because it verifies that it did. The floor is structural rather than advisory — ChunkData’s field is private, and its constructor and decode gate both reject an empty payload — so it cannot be relaxed by forgetting to call a validator (#1145 review).

At least one byte having already arrived. The reset is what makes a stall the peer’s fault, so before the FIRST byte there has been no reset and the argument does not apply: the clock is measuring the server’s time-to-first-byte, which scales with blob size (the serve path materialises the whole bao wire via export_bao_range before it can emit chunk #1). Both loops therefore raise PullTimeout — exonerating — when the budget elapses at cumulative == 0, and this sentinel only once bytes have flowed (#1145 review). Without that split, a 1 GiB blob off a cold disk would score an honest server as unreachable for the crime of being big.

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.

after: Duration

The inactivity budget that elapsed after bytes had been flowing.

Trait Implementations

impl Debug for PullStalled

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

Formats the value using the given formatter.

impl Display for PullStalled

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

Formats the value using the given formatter.

impl Error for PullStalled

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.