Skip to main content

transitive_convergence_over_a_partial_mesh

Function transitive_convergence_over_a_partial_mesh 

Source
pub async fn transitive_convergence_over_a_partial_mesh<F: SyncFixture>(
    open: impl AsyncFn() -> F,
) -> Result<RuleOutcome, Violation>
Available on crate feature proptest only.
Expand description

SY-24 and SY-4: after every link heals and the peers settle, every peer holds every event written anywhere, byte for byte — including peers that never met the event’s origin.

A missing event is classified by what the model saw: never offered to that peer is SY-24 (not forwarded); offered and acknowledged as appended is SY-4 (quarantined); offered and acknowledged as already held when it never was is SY-1.

§Rejects

A peer that holds guarded events back for review and acknowledges them as appended: the quarantine design SY-4 names. tests/wrong_topologies.rs carries it, and only a generated case can catch it, so it is also the end-to-end check that a failure prints its seed. And a peer that dedupes by the highest position seen per origin, which drops an event that arrives after a later one from the same origin; that is caught by the pinned regression delayed_page_lands_after_a_later_one. And a peer whose caught-up resume token points one group past the end of its log, so the next group it takes in is never forwarded along a lane that had caught up: SY-24 itself.

§Errors

A Violation of SY-4, SY-1 or SY-24 for a peer missing an event, and of SY-24 for a peer that refuses a push or a pull or never settles.