docs: chunk-cache order fix in the changelog and known issues

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
2026-09-27 08:03:24 -05:00
parent 4ad80736f4
commit 175d3a1f50
2 changed files with 15 additions and 2 deletions
@@ -2,6 +2,15 @@

 ## Unreleased

+### Deterministic errors on damaged chunked datasets (2026-09-27)
+- A read through the file's chunk cache listed a damaged dataset's chunks in
+  hash-map order, seeded per `File`, so two opens of the same file could
+  report different failing chunks (`cve-2025-2310.h5`, and an intermittent
+  failure of the storage and wasm corpus comparisons). The cache now keeps
+  the chunk index's own order, as the uncached readers use: every path names
+  the same first damaged chunk. Values of readable datasets were never
+  affected.
+
 ### Range reads, milestone M5: reading files a SWMR writer is appending to (2026-09-27)
 Design: `docs/design/swmr.md`.
 - **Fix: files with the SWMR-write flag were bounded by a stale end of