v3.7.1 — Phase 5 Part 5: Configurable Consistency Levels + Isolated Test Runner #45
Jovancoding
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Three Consistency Modes
eventualsessionclearSession()to flush the cachestrongwriteAsync()callsflush()on anyFlushableBackend(e.g.RedisBackend) after each write before returningNew Exports
ConsistentBackendBlackboardBackendwith consistency semanticsConsistencyLevel'eventual' | 'session' | 'strong'FlushableBackendflush(): Promise<void>isFlushable(backend)trueif backend implementsFlushableBackendIsolated Test Runner
run-tests.tsreplaces the old chained&&command intest:all. Each suite now runs as an isolated child process (spawnSync+--max-old-space-size=512), fully cleaned up before the next starts — no more VS Code terminal crashes on full test runs.npm run test:all # or: npx ts-node run-tests.tsTesting
test-phase5e.ts) — all three modes, session overlay/delete/listKeys/snapshot, strong flush integration, TTL, instance independence, export verificationNo Breaking Changes
All existing backends (
FileBackend,MemoryBackend,RedisBackend,CrdtBackend) are unchanged.ConsistentBackendis opt-in.Full Changelog
See CHANGELOG.md for details.
Beta Was this translation helpful? Give feedback.
All reactions