SQLite Error 19: 'UNIQUE constraint failed: MediaFile.Path' this means the file is already in the etv database
#New media not being found
smoky hemlock
do you also have it in a local library?
smoky hemlock
the other reason that can happen is when you have multiple episodes in a single file, probably more likely here with lost s06e01 and s06e02. it doesn't really impact anything other than metadata (only shows one of the episodes in etv).
i would update to the latest develop release, it no longer needs files on local disk - it gets all info it needs directly from plex, so you don't have to mess with path replacements
see the channel description in #features-and-changes
smoky hemlock
yeah, the db should be sufficient. maybe turn sync off for the library in the old version, then turn it on in develop
waxen harbor
Hey mystified I have the same issue. Have you recently replaced the version of the file you are using? I.e. upgrading from 720p to 1080p but keeping the same file name?
smoky hemlock
im sorry i misread your earlier posts - i didn't see that you said the scan stops after that error. if that's the case that's a bug and one that i should be able to easily fix
testing with multi-episode files now, if that doesn't trigger it i'll also try replacing a file
waxen harbor
in my experience, it seems to be only if the file name doesn't change (which would make sense because the SQL database is demanding a unique file name it seems)
smoky hemlock
no luck yet - im trying a bunch of things with multi-episode files, and replacing files with different files (keeping the same name). it correctly updates in that case
yep
somehow plex is sending it as a different item (with a unique plex key) but the same path. there must be some order of operations that i don't have right. everything i do has plex sending it with the same key
maybe if i remove, scan in plex, add new, scan in plex, then scan etv again...
ill add some debug logging to try to get an idea
if you can dm me your ersatztv.sqlite3 db from the config folder (plex api key is stored elsewhere), and then run the new version once it builds that new log output with your db should give some clue
it's going to say Updating plex episode (key {Key}) path from {Existing} to {Incoming}
okay, all docker images are updated if you're able to scan again
smoky hemlock
nm, it crashes before that. ugh
smoky hemlock
alright, just pushed something that should let it work through that error at least (won't fix it yet). should be ready in 20 min or so
waxen harbor
seems to be powering through for me
smoky hemlock
cool, np. there's a mismatch between how plex handles multiple versions and how etv does. trying to brainstorm if i can clean it up a bit, but glad it unblocked your scans