Review history drops older reports that still fit

Offen
  • Stimmt etwas nicht?
#596 2 Kommentare 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

@HellHBBD arbeitet bereits daran.

Seit 06.11.2026.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Beschreibung

Observed behavior

The browser-local review archive prematurely drops older reports, even when the 500-entry limit and the 164 KiB byte budget would allow them to be retained.

In web/history.js, boundedReviews() limits the input to the first 500 candidates before checking whether each report fits the remaining byte budget. A skipped report still consumes an input position, preventing an older report from being considered.

In a deterministic reproduction, saving three large reports into an initially full 500-entry archive leaves only 499 reports after the third save. An older report (old-497) disappears even though retaining it would keep the archive within both limits.

This affects browser-local report history. The reproduction does not demonstrate account-database report loss.

Expected behavior

A report that cannot fit within the remaining byte budget should be skipped without consuming a retained-report slot.

Older candidates should continue to be considered until either 500 reports have been retained or all available candidates have been examined.

In the reproduced scenario, the archive should retain exactly 500 reports, including old-497, totaling 160,917 bytes, below the 164 KiB (167,936 bytes) budget.

Existing newest-first ordering, UTF-8 byte accounting, code stripping, and short-history retention should remain unchanged.

Reproduction

Reproduced using the real history persistence module on upstream main at commit b2c2bc9aca5e9e70f28ff2a16e4bd0b2d5e87a2f, with Node.js v26.12.1, in-memory storage, and a mocked signed-out session.

Steps to reproduce
  1. Seed codetrial_review_history with 500 small reports, old-0 through old-499.
  2. Seed codetrial_history with the newest 20 entries.
  3. Call saveReportHistory() three times with distinct reports containing 56,000-character summaries.
  4. Inspect the retained review archive after each save.
Observed results
  • First save: 500 retained reports, 104,904 bytes; oldest retained: old-498.
  • Second save: 500 retained reports, 160,917 bytes; oldest retained: old-497.
  • Third save: 499 retained reports, 160,819 bytes; oldest retained: old-496.

After the third save, old-497 is missing. Restoring it would produce 500 reports totaling 160,917 bytes, below the 164 KiB (167,936 bytes) limit.

The failure is deterministic with this setup. The reproduction uses mocked browser storage rather than an interactive interview.

CodeTrial version

codetrial 0.1.0 (b2c2bc9)

Environment

OS: Arch Linux
Browser: Not applicable; reproduced under Node.js v26.12.1 with mocked browser storage.
Language: Not applicable.
Interview loop: Not applicable; no interview session was started.
Problem: Not applicable; browser-local review-history persistence.
REACTO or STAR step: Not applicable.
Reconnect: Not applicable.

Reproduction environment: Real web/history.js persistence module, in-memory storage, and a mocked signed-out /api/session response.

Sanitized evidence

The regression assertion fails on the unmodified upstream implementation:

AssertionError: Archive should retain 500 reports when another older report fits

499 !== 500

Relevant implementation (web/history.js, lines 462-489):

https://github.com/sysprog21/codetrial/blob/b2c2bc9aca5e9e70f28ff2a16e4bd0b2d5e87a2f/web/history.js#L462-L489

for (const row of reviews.slice(0, REVIEW_HISTORY_CAP)) {

The input is truncated before the byte-budget check. Candidates skipped for exceeding the remaining budget still occupy positions within the first 500 inputs, so older candidates are not considered.

The existing oversized-review test in tests/browser/account.test.js (lines 864-880) does not cover this interaction between a full 500-entry archive and byte-budget rejection.

https://github.com/sysprog21/codetrial/blob/b2c2bc9aca5e9e70f28ff2a16e4bd0b2d5e87a2f/tests/browser/account.test.js#L864-L880

Related work: #221 and PR #321 address final-code retention, not this premature review-archive eviction.

The reproduction uses synthetic report identifiers and summaries. No credentials, session tokens, recordings, or personal interview content are included.

Public data confirmation
  • I removed credentials, session tokens, candidate recordings, and personal interview content from this public report.
Vorherrschende Sprache
Rust
Sterne
223
Forks
148
Ø Merge
1 T. 10 Std.
Gemergte PRs (30 T.)
227

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus sysprog21/codetrial

Alle Issues in sysprog21/codetrial

Ähnliche Issues

Weitere Issues zu Rust

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.