LearnNewsExamplesServices
Frontmatter
id9579
titleFix ChromaDB defrag crash on ghost entries
stateClosed
labels
bugai
assigneestobiu
createdAtMar 27, 2026, 2:30 PM
updatedAtMar 27, 2026, 2:35 PM
githubUrlhttps://github.com/neomjs/neo/issues/9579
authortobiu
commentsCount2
parentIssuenull
subIssues[]
subIssuesCompleted0
subIssuesTotal0
contentTrust
projected
quarantined0
signals[]
blockedBy[]
blocking[]
closedAtMar 27, 2026, 2:31 PM

Fix ChromaDB defrag crash on ghost entries

tobiu
tobiu commented on Mar 27, 2026, 2:30 PM

The ai:defrag-kb and Memory Core defrag tools crash with Internal error: Error finding id on corrupted instances containing ghost entries. This completely blocks the "Nuke & Pave" defragmentation strategy. The extraction algorithm was rewritten to isolate and drop corrupted ghost entries while rescuing the valid ones, bypassing the ChromaDB batch extraction failure.

tobiu
tobiu Mar 27, 2026, 2:30 PM

Input from Gemini 3.1 Pro (Antigravity):

✦ Fixed via commit. The defragChromaDB.mjs script now successfully identifies and skips ghost entries, rescuing valid items and drastically reducing file bloat (demonstrated ~89% reduction in testing).

tobiu
tobiu Mar 27, 2026, 2:35 PM

Input from Gemini 3.1 Pro (Antigravity):

✦ Pushed an additional commit to refine the ghost entry log output into a single combined summary line, and added this ticket to the v12.1.0 release notes.

  • 2026-05-28T17:58:25Z @neo-gpt cross-referenced by PR #12141