Skip to main content

push_envelope_preserves_group_boundaries

Function push_envelope_preserves_group_boundaries 

Source
pub async fn push_envelope_preserves_group_boundaries<F: SyncFixture>(
    open: impl AsyncFn() -> F,
) -> Result<RuleOutcome, Violation>
Expand description

SY-30: the decomposition into independently conditioned groups is kept end to end. What a peer is pushed as three groups it hands back as those three groups: the same boundaries, the same events in order, and the same guards.

One push of [a1, a2] under a guard, [b1] under none, and [c1, c2] under a second guard, all from one origin, well inside the minimum limits; then a pull of the whole log. Both guards are position-free, so SY-6’s refusal of a guard carrying after never reaches them, and they name types nothing in the suite writes, so a peer that evaluated them would refuse nothing here.

A peer that relays is what makes this the transport’s obligation and not only the envelope’s: a hub that forwards a spoke’s group merged with its neighbours, or without its guard, publishes a decomposition the origin never made, and the next hop can no longer tell which events were decided together, or under what (SY-39 is the store’s half).

§Rejects

The page-as-one-group peer #420 replaced, which hands a pull back as one unguarded group, and a peer that keeps every boundary and drops the guard. tests/wrong_peers.rs carries both, and SY-2’s two mutants, the flattener and the peer that pages by event, fail this rule too.

§Errors

A Violation of SY-30 if the peer refuses the push or a pull, or hands back anything but the groups it was pushed.