Skip to main content

store_accepts_the_guaranteed_minimum_payload

Function store_accepts_the_guaranteed_minimum_payload 

pub async fn store_accepts_the_guaranteed_minimum_payload<F: Fixture>(
    open: impl AsyncFn() -> F,
) -> RuleOutcome
Expand description

A payload at the guaranteed minimum is accepted whole.

VT-21, which states a floor rather than a ceiling: there is no MAX_EVENT_DATA_LEN, every store MUST accept 65,536 bytes, and a store that refuses more MUST say so with a distinguishable error rather than truncating. This rule owns the floor; the refusal is append_reports_exceeded_store_limits, which needs the AppendError::ExceedsStoreLimit variant VT-25 introduces at phase 4.

What it rejects is an undocumented row-size ceiling — a payload stored inline in a fixed-width column, or a KV backend with a per-value cap the adapter never states. Both of the engine’s answers to that are compiled, and the rule needs both because they fail at different places: PayloadCeilingStore refuses, which the append_ok above catches before the round trip runs at all, and TruncatingPayloadStore accepts and stores a prefix, which is what the length assertion below is for. VT-21’s MUST names the second — “refuse an oversized payload … rather than truncating” — and until stage 6’s review nothing rejected it. Both sit at 4 KiB, which is the shape rather than a specific product.

The clause is [PROVISIONAL] and phase 4 freezes it. The number is read from VT-21, not from happenstance-core, because the constant it mandates does not exist yet.