summaryrefslogtreecommitdiffstats
path: root/packages/meshbay-node/src/meshbay_node/indexer/enrich.py
diff options
context:
space:
mode:
authorChristophe Besson <cbesson@gmail.com>2026-08-26 15:36:23 +0200
committerChristophe Besson <cbesson@gmail.com>2026-08-26 15:36:23 +0200
commit84aa73e89cfe486c62317f761dcf87d7845eb4f7 (patch)
tree35b655fa27340ca6295f00daaa72a014c8f58c56 /packages/meshbay-node/src/meshbay_node/indexer/enrich.py
parent4c45792c861c47d44ebdbbab4130e37fba5d6795 (diff)
downloadmeshbay-84aa73e89cfe486c62317f761dcf87d7845eb4f7.tar.gz
fix(video): TMDB match cache never invalidated on movie<->show reclassification
The real reason a node restart alone didn't fix already-indexed entries after the previous commit's enrichment change: _do_media_meta_request checked media_cache's file->tmdb mapping (keyed by content hash) and trusted it unconditionally, before ever comparing it against the file's *current* movie/show classification. A file whose season/episode changed on a later scan — exactly what the Specials-folder fix does, for every file it reclassifies from "movie" to "tv" — kept answering with its stale, wrong-kind-of-match forever, since nothing about a reclassification touches this cache or its key. Now falls through to a fresh search whenever the cached media_type disagrees with what the entry resolves to right now, rather than trusting a mapping that predates the file's current classification.
Diffstat (limited to 'packages/meshbay-node/src/meshbay_node/indexer/enrich.py')
0 files changed, 0 insertions, 0 deletions