Memvid Files

v2.0.138

Release Date: March 3, 2026

Overview

This release fixes two SDK issues: lex_enabled/vec_enabled state not persisting after re-opening .mv2 files, and ask() crashing with "frame id out of range" on files with inconsistent time indexes.

🐛 Bug Fixes

lex_enabled/vec_enabled reset to None on re-open — Issue [#194]

• Added lex_enabled and vec_enabled fields to the core Stats struct so SDKs can read runtime search engine state
• Python SDK now auto-detects vec_available from disk state when opening a file (matches the pattern already used in ask())
• stats() in both Python and Node SDKs now includes lex_enabled and vec_enabled keys
• Previously, use() with default enable_vec=False would report vec_available=false even when the file contained a vec index, causing find(mode="semantic") to error immediately

ask() "frame id out of range" on fresh .mv2 files — Issue [#196]

• build_timeline() now gracefully skips time index entries that reference out-of-range frame IDs instead of returning a hard error
• Logs a tracing::warn! for observability when skipping invalid entries
• This matches the existing graceful-skip pattern used in ask.rs fallback timeline responses

📚 Related Issues

• [#194] — lex_enabled/vec_enabled reset to None on re-open
• [#196] — ask() "frame id out of range" on fresh .mv2 files