test: remove check tail assertion from correctness test #55
Conversation
Greptile SummaryRemoves the post-run
Confidence Score: 5/5Safe to merge — removes one assertion from a test file with no production code changes. The deleted check_tail assertion was logically incorrect on persistent streams where retry-driven duplicates push tail.seq_num beyond TOTAL_RECORDS. The remaining consumer-side assertions still fully cover the gapless-read invariant the test was designed to verify, so no coverage gap is introduced. No files require special attention. Important Files Changed
Sequence DiagramsequenceDiagram
participant Test as Test (TaskGroup)
participant Producer as append_records()
participant Consumer as read_records()
participant Stream as S2Stream
par concurrent tasks
Producer->>Stream: "producer.submit(Record(body=str(i))) x 1024"
Stream-->>Producer: ticket (per record)
Producer->>Stream: await ticket x 1024
Stream-->>Producer: "ack.seq_num >= 0"
Consumer->>Stream: "read_session(start=SeqNum(0), limit=count(1024), wait=60)"
Stream-->>Consumer: batches of records
Consumer->>Consumer: "assert seq_num == last_seq_num + 1 (gapless)"
Consumer->>Consumer: "assert 0 <= index < 1024 (valid body)"
Consumer->>Consumer: "assert index <= highest_contiguous_index + 1"
end
Note over Test: After TaskGroup completes
Consumer->>Consumer: "assert highest_contiguous_index == 1023"
Consumer->>Consumer: "assert last_seq_num == 1023"
Consumer->>Consumer: "assert observed_records == 1024"
Note over Test: check_tail assertion removed - tail.seq_num may exceed 1024 when retries produce duplicates
Reviews (2): Last reviewed commit: "initial commit" | Re-trigger Greptile |
|
@greptileai addressed your comment. pls review again and update your score. |
No description provided.