FAILURE MAP
← Case archive

FA-11173 / Streaming segment lifecycle / Member archive

Append failure keeps uncommitted segment · case 03

Append completion is treated as success even when the decoder rejected the segment.

Member previewVariant 3 · 3 implementations · 4 checks per implementation

Case contract

An inflight segment becomes committed only after successful append; failure retains its ID for recovery and leaves committed order unchanged.

Why this case matters

A deterministic local media controller stage; metadata and downloaded data are supplied explicitly. No external player, service or codec is required.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixtureActualExpectedOutcome
fixture 1[["a", "b"], null][["a"], "b"]Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.

Sign in to the archive ↗