Memvid Files

v2.0.139

Release Date: March 13, 2026

Overview

This release completes the fix for MV005 (Time index track is invalid: frame id out of range) by extending graceful stale frame_id handling to all search paths — find(), ask(), Tantivy, lex fallback, vec search, and temporal metadata lookups.

🐛 Bug Fixes

MV005 crash in find() and ask() search paths — Issue [#196] (continued)

• v2.0.138 fixed the timeline.rs path only; stale frame_ids in Tantivy evaluation, snippet assembly, lex fallback, and temporal metadata lookups still caused hard crashes
• All 5 search-path locations now gracefully skip stale frame_ids with tracing::warn! instead of returning MV005 errors
• Added stale_index_skips counter on SearchResponse so callers can detect index degradation
• Exposed stale_index_skips in both Python and Node SDK responses (only present when > 0)
• CLI search command updated to include the new field

Root cause: Search indexes (Tantivy/lex) can hold frame_ids that no longer exist in toc.frames due to instant_index writing WAL sequence numbers, stale on-disk lex segments, or reopening files where the index loaded from a prior state.

📚 Related Issues

• [#196] — ask() fails with "Time index track is invalid: frame id out of range"
• [#204] — commit() raises AttributeError on _MemvidCore (tracked, not addressed in this release)