diff options
| author | Christophe Besson <cbesson@gmail.com> | 2026-08-26 17:13:32 +0200 |
|---|---|---|
| committer | Christophe Besson <cbesson@gmail.com> | 2026-08-26 17:13:32 +0200 |
| commit | ca62b4123b854fc9ece258e14c84c895aaa275cd (patch) | |
| tree | 458b8901cbd590f12463c8623b54ae91b5c42b88 /packages/meshbay-node/tests/test_title_parse.py | |
| parent | db7f81fd08742847f3ebea061c75530b7b31b934 (diff) | |
| parent | 3d03692b6cc5e47c4bb49b86707a50cdaa5408f2 (diff) | |
| download | meshbay-ca62b4123b854fc9ece258e14c84c895aaa275cd.tar.gz | |
Merge branch 'fix/tmdb-override-metadata'
An operator's "fix match" correction only ever recorded the file->tmdb_id
mapping, never the metadata that id actually names — so the very next
lookup found nothing cached under the new id and fell straight through to
a fresh automatic search, silently reproducing the original wrong match.
Invisible for two shows whose own title happened to be enough for that
fallback search to land on the right answer anyway; surfaced on a movie
whose own title search kept landing on the same wrong match regardless of
the override.
Verified live after this fix: the same "fix match" action, redone, made
the correction stick this time.
Diffstat (limited to 'packages/meshbay-node/tests/test_title_parse.py')
0 files changed, 0 insertions, 0 deletions