Skip to content

chore(deps): bump memvid-core from 2.0.138 to 2.0.139#149

Open
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/cargo/memvid-core-2.0.139
Open

chore(deps): bump memvid-core from 2.0.138 to 2.0.139#149
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/cargo/memvid-core-2.0.139

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot bot commented on behalf of github Mar 20, 2026

Bumps memvid-core from 2.0.138 to 2.0.139.

Release notes

Sourced from memvid-core's releases.

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

  • #196ask() fails with "Time index track is invalid: frame id out of range"
  • #204commit() raises AttributeError on _MemvidCore (tracked, not addressed in this release)
Commits
  • a79dfdd v2.0.139: Fix MV005 — graceful handling of stale frame_ids in all search paths
  • See full diff in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [memvid-core](https://github.com/memvid/memvid) from 2.0.138 to 2.0.139.
- [Release notes](https://github.com/memvid/memvid/releases)
- [Changelog](https://github.com/memvid/memvid/blob/main/CHANGELOG.md)
- [Commits](memvid/memvid@v2.0.138...v2.0.139)

---
updated-dependencies:
- dependency-name: memvid-core
  dependency-version: 2.0.139
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file rust Pull requests that update rust code labels Mar 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file rust Pull requests that update rust code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants