Download Latest Version v3.3.5 -- integrity, recovery, and cross-process correctness source code.tar.gz (24.3 MB)
Email in envelope

Get an email when there's a new version of MemPalace

Home / v3.3.5
Name Modified Size InfoDownloads / Week
Parent folder
README.md 2026-05-10 14.0 kB
0
v3.3.5 -- integrity, recovery, and cross-process correctness source code.tar.gz 2026-05-10 24.3 MB
0
v3.3.5 -- integrity, recovery, and cross-process correctness source code.zip 2026-05-10 24.4 MB
5 5 weekly downloads
Totals: 3 Items   48.8 MB 5

3.3.5 is a fixes release. No new user-facing features — the cycle's energy went into data integrity, recovery, and cross-process correctness. If your palace ever hit Internal error: Error finding id after a big mine, or you had a knowledge-graph triple silently disappear into the void, or you're running on Windows / a multi-tenant host — this release is for you.

The headline fixes:

  • mempalace repair --mode from-sqlite recovers palaces stuck on apply_logs. When ChromaDB's HNSW segment writer wedges (the corruption class reported upstream and in [#1308]), --mode legacy and the inline repair both call Collection.count() as their first read — which is exactly the call that raises. The old failure mode was a repair printing Cannot recover — palace may need to be re-mined from source files even though the SQLite tables were fully intact. The new mode reads (id, document, metadata) directly from chroma.sqlite3 via the metadata segment join, never opens a chromadb client against the corrupt palace, and re-upserts everything into a fresh palace under your configured embedding function. Verified end-to-end on a 52,300-row real-world corrupt palace. (#1308)

  • Two silent-loss classes in the knowledge graph are now write-time errors. Triples with valid_to < valid_from used to be durably stored but unreachable (the temporal filter matched no as_of); add_triple() now rejects inverted intervals at write time. And date strings forwarded to SQLite are validated up front via sanitize_iso_temporal() (alias sanitize_iso_date()), which accepts YYYY-MM-DD and canonical UTC datetimes (YYYY-MM-DDTHH:MM:SSZ / +00:00) and rejects everything else — natural-language inputs like "yesterday" no longer silently produce empty result sets. Behavior change: partial-date inputs that worked in 3.3.4 ("2026", "2026-05") now error; pass a full date or canonical UTC datetime instead. (#1214, [#1164], [#1167], [#1374], [#1417])

  • EntityRegistry.save() is now crash-safe. The people/projects map is months of mining data, and the old code did a non-atomic Path.write_text() — a power loss, OOM, or kill -9 between truncate and full-flush would silently wipe it (the registry's load() swallows JSONDecodeError). Save now writes to a sibling temp file, fsyncs, and os.replace()s into place. The previous registry stays intact on any crash before the rename returns. (#1215)

  • MCP tool_search rides through the post-bulk-mine HNSW flush window. After a CLI mine, ChromaDB's HNSW segment metadata can be unflushed for ~30-60s; wing-scoped MCP search was hitting Internal error: Error finding id for that entire window. tool_search now detects this specific transient, drops both the MCP-local and shared-backend caches for the palace, sleeps 2s, and retries once. Successful retries are tagged with index_recovered: true so callers can observe when it fired. Partial fix for the broader [#1315] cluster — tool_check_duplicate and other index-touching tools still need the same wrapper. (#1396)

  • Cross-process correctness on Windows and multi-tenant hosts. ChromaBackend.close_palace() now properly releases ChromaDB's rust-side SQLite file lock — reopening the same palace path after shutil.rmtree no longer fails with SQLITE_READONLY_DBMOVED. And the MCP server's _kg is no longer a module-level singleton: multi-tenant hosts rotating MEMPALACE_PALACE_PATH between tool calls now hit the right SQLite file via a lazy per-path cache. (#1067, [#1105], [#1136], [#1160])

  • Windows stdio is UTF-8 across the board. mempalace search > out.txt and piped fact_checker invocations no longer mojibake Cyrillic / CJK drawer text at the process boundary. mcp_server, hooks_cli, and cli/fact_checker all reconfigure identically. (#1282)

  • miner.detect_room routing fix for monorepos. The substring check was bidirectional, so any token that was a substring of a room name or vice versa matched — views/billing-page/src/Foo.test.tsx routed to an interviews room because "views" in "interviews" matched first. Now uses separator-bounded token matching (-, _, ., /). (#1004, closes [#1002])

  • mempalace compress no longer crashes on palaces above ~32k drawers. Drawer fetch is now paginated, mirroring the [#851] fix in miner.py. (#1073, [#1107])

Internal: test reliability got a pass too — tests/test_palace_locks.py and tests/test_chroma_collection_lock.py switched from fork to spawn for subprocess spawning (Python 3.13 + multi-threaded parent = deadlock under fork, and macOS forbids fork-without-exec via CoreFoundation), and several test files now wrap sqlite3.connect(...) in contextlib.closing() so connections release on the failure path too. (#1430, [#1431])

The promises haven't moved. Every word stored exactly. Everything stays on your machine. No telemetry. No fallbacks to cloud APIs we didn't tell you about. Each release sharpens what's already there.

What's Changed

New Contributors

Full Changelog: https://github.com/MemPalace/mempalace/compare/v3.3.4...v3.3.5

Source: README.md, updated 2026-05-10