|
|
před 1 měsícem | |
|---|---|---|
| .. | ||
| 2026-04-19-snapshot-truncation.md | před 1 měsícem | |
| 2026-04-22-eviction-induced-write-loss-plan.md | před 1 měsícem | |
| 2026-04-22-zoe-rss-exceeds-budget.md | před 1 měsícem | |
| README.md | před 1 měsícem | |
All incidents here are resolved. They were previously top-level BUG-*.md
files whose status headers still read "Open", which is no longer true. The
lessons are folded into CLAUDE.md; these are the long-form originals.
| File | Resolution |
|---|---|
2026-04-19-snapshot-truncation.md |
Fixed in v1.6.1. The snapshot writer became atomic - write .tmp, fsync, rename, then verify by re-reading. A loader fallback chain and the MySQL-style recovery modes landed with it. |
2026-04-22-zoe-rss-exceeds-budget.md |
Superseded by v2.0. The original "memory leak" framing was wrong: v2.4.3 established that estimatedMemoryBytes_ under-reports by roughly 5x, so eviction never believed it had made progress. Since v2.0 RSS is bounded by the LMDB mapsize plus OS page cache, not by MemoryStore eviction, and max_memory_mb only sizes the mirror cache. |
2026-04-22-eviction-induced-write-loss-plan.md |
Shipped in v1.7.x. Became chunked pressure-aware eviction (four pressure levels, hot-write floor, quiesce on in-flight writes, no per-collection mutex held during disk I/O) plus the conf.d drop-in config mechanism. v2.4.3 later added the episode cap and no-progress detector after eviction drained a live store. |
Anything still open lives in docs/ROADMAP.md under "Pending", not here.