FAILURE MAP
← Case archive

FA-76232 / Chat ordering and read receipts / Member archive

Place "seen by" avatars under the latest read message: avatar order · case 02

Avatars under a message are sorted by user id instead of most recent reader first.

Member previewVariant 2 · 3 implementations · 6 checks per implementation

Case contract

messages are ascending [seq, author] of the visible window. reads maps user -> [read_seq, read_at]. Each user other than me gets an avatar under the latest visible message with seq <= read_seq; users whose read_seq is before the first visible message get none. Avatars under one message are ordered by read_at descending, then user id. Result: [[seq, [users...]]...] by seq.

Why this case matters

"Seen by" rows show how far each participant has read; misplacement misreports who saw what.

One recorded failure

Sample boundary fixture

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

Boundary fixtureActualExpectedOutcome
several readers same message[[2, ["al", "bo", "cy"]]][[2, ["cy", "al", "bo"]]]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 ↗