David Snelling
54c183668c
The async group-commit flush that persists single-op generation history swallowed persist failures as a bare warn: writes kept succeeding while their before-images piled up in memory, never durable and unbounded, with no signal. The generation store now accounts for every failed flush at one place (flushPendingSingleOps), tolerates a transient blip (retry with capped exponential backoff), and after PENDING_FLUSH_FAILURE_THRESHOLD consecutive failures LATCHES a durability failure and refuses further single-op and transact writes with a typed, exported PendingFlushDurabilityError — rather than promise a durability it cannot deliver. Live canonical data is untouched; only the immutable history is stuck. The latch self-heals: the moment a flush succeeds (a retry, or an explicit flush()/close()) it lifts and writes resume. Loud errors, never quiet losses. |
||
|---|---|---|
| .. | ||
| bounded-chains.test.ts | ||
| db-portable-graph.test.ts | ||
| generation-chain.test.ts | ||
| generationStore.test.ts | ||
| pending-flush-durability.test.ts | ||
| stableEqual.test.ts | ||
| whereMatcher.test.ts | ||