Memtrace v1.1.12

Memtrace v1.1.12

Hosted stores index at full speed again

New

• New features land on Nightly first: npm install -g memtrace@nightly is the same memtrace command, and it is not always stable. They still ship on the default install. memtrace install stays on the channel you already have.

Fixed

• A graph cache that outlives its store no longer stalls a start. When the store behind a workspace is reset or written by another release, the cache files under .memdb/graph-cache can no longer be proven complete; 1.1.10 re-read them on every refresh, kept the repositories queued, and waited out remote scan deadlines between repositories, up to 21 minutes each. A cache that fails the proof is now evicted at the first rejection and rebuilt from the store.
• The per-repository insight card printed during memtrace start is limited to 30 seconds; when the graph is busy the card is skipped and the next repository starts at once.
• Startup embedding no longer vanishes when cross-repo linking is still settling. A repository whose embedding had to wait is listed as deferred in the memtrace start summary and embedded automatically once the graph settles, instead of being counted as embedded.
• A repository whose graph was rebuilt during memtrace start (a fresh index, or the self-heal regeneration) is always embedded in that same start, even when the restart shortcut would otherwise skip the full pass. Such a repository could previously finish the start with no vectors at all.
• A repository that an earlier start left without vectors is embedded at the next memtrace start. The restart shortcut that skips embedding when HEAD is already indexed now also requires the embedding-complete marker for that HEAD.
• Indexing against a hosted MemDB is dramatically faster. Memtrace read records from the store four at a time, a width picked for a database on the same machine where a read costs CPU. On a hosted database a read costs a network round trip instead, so that width capped the client at about 125 records a second and a workspace that used to index in minutes could run for hours with both machines almost idle. Memtrace now measures the round trip to its store and reads as wide as that justifies, and sizes the connection for a remote database. A local database keeps exactly the width it had. MEMTRACE_STORE_READ_CONCURRENCY pins it if you need to.
• memtrace no longer reports the database connection as lost when it was not. A single failed request marked the connection down before anything had checked it, so a recovered hiccup logged a "connection lost" warning that the next line contradicted. The connection is reported lost only once a repair attempt has actually failed, and the reason it failed is logged with it.

Install

npm install -g memtrace