Closed isidornygren closed 2 years ago
@vitiko98 did you had time to look into this one?
My theory: this bug is impossible to reproduce by just running guessit
CLI because is a product of preliminary guessit
runs during bazarr
runtime; thus, the only way to try to reproduce it is by knowing the source of previous runs.
Please send me your Bazarr database (located at data/db
) to averroista@protonmail.com
@vitiko98 could it be related to some old garbage here that didn't age well when we move from Python 2.7 to 3.x?
https://github.com/morpheus65535/bazarr/blob/development/libs/subliminal_patch/core.py#L743-L758
I'm not even sure it's required... we could simply parse the actual file path with guessit.
@vitiko98 could it be related to some old garbage here that didn't age well when we move from Python 2.7 to 3.x?
https://github.com/morpheus65535/bazarr/blob/development/libs/subliminal_patch/core.py#L743-L758
I'm not even sure it's required... we could simply parse the actual file path with guessit.
It could be. Neither do I believe that code block is required anymore.
OP already sent me the database. I'll try to reproduce the bug within the next hours
Having the same issue on v1.0.4
BAZARR Error (An internal error has occured in guessit.===================== Guessit Exception Report =====================version=3.4.3string=The Boys (2019) [tvdb-355567]/Season 2/The Boys S02E06 The Bloody Doors Off 1080p AMZN WEB-DL DDP5 1 H 264-NTb.mkvoptions={'expected_title': ['OSS 117', 'This is Us', 'The Boys'], 'allowed_countries': ['au', 'gb', 'us'], 'allowed_languages': ['ca', 'cs', 'de', 'en', 'es', 'fr', 'he', 'hi', 'hu', 'it', 'ja', 'ko', 'mul', 'nl', 'no', 'pl', 'pt', 'ro', 'ru', 'sv', 'te', 'uk', 'und'], 'advanced_config': {'common_words': ['ca', 'cat', 'de', 'he', 'it', 'no', 'por', 'rum', 'se', 'st', 'sub'], 'groups': {'starting': '([{', 'ending': ')]}'}, 'audio_codec': {'audio_codec': {'MP3': {'string': ['MP3', 'LAME'], 'regex': ['LAME(?:\d)+-?(?:\d)+']}, 'MP2': 'MP2', 'Dolby Digital': {'string': ['Dolby', 'DolbyDigital'], 'regex': ['Dolby-Digital', 'DD', 'AC3D?']}, 'Dolby Atmos': {'string': ['Atmos'], 'regex': ['Dolby-?Atmos']}, 'AAC': 'AAC', 'Dolby Digital Plus': ['EAC3', 'DDP', 'DD+'], 'FLAC': 'Flac', 'DTS': 'DTS', 'DTS-HD': {'regex': ['DTS-?HD', 'DTS(?=-?MA)'], 'conflict_solver': "lambda match, other: other if other.name == 'audio_codec' else 'default'"}, 'Dolby TrueHD': {'regex': ['True-?HD']}, 'Opus': 'Opus', 'Vorbis': 'Vorbis', 'PCM': 'PCM', 'LPCM': 'LPCM'}, 'audiochannels': {'1.0': ['1ch', 'mono', 're:(1[\W]0(?:ch)?)(?=[^\d]
$)'], '2.0': ['2ch', 'stereo', {'regex': '(2[\W_]0(?:ch)?)(?=[^\d]
I hope this bug is gone in the upcoming beta.
I updated to 1.0.5-beta.34. Appears to be resolved.
Describe the bug Most (if not all) of my files fails during checking. Seems to be something going on with Guessit. However, when I run Guessit manually on the afflicted files, it returns a correct guess. Therefore, I'm not sure that this is an issue directly tied to Guessit.
Screenshots
Software (please complete the following information):
Additional context Logfile: