New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not recognising date style identifiers #1393
Comments
Did you try |
I did not, but I just now tried changing the line to:
but it doesn't validate the config, giving me this:
I tried updating with pip, but it seems I've already got the latest. I should probably clarify that the date auto-detection had been working for years against the same date format, without a need to specify the ID type in any way. I only added the |
Those options go alongside the identified_by one, like: identified_by: date
date_yearfirst: yes |
Oh I see, thanks! It's cool with those as separate config options. |
Works for me. |
Strange. I'm still getting a huge pile of messages like in the log snippet above, but somehow this one show got recognised and downloaded, thus I'm getting this message as normal:
|
Looks good to me:
output:
I think we can we close this. |
Unable to replicate. Closing. If you find a way to replicate it with a fresh database, then feel free to reopen. |
Updated with pip. That specific example works now, but 90% do not. Tried with a new database and minimal config. |
Here is the log. There should be plenty of examples to play with there. Also, I don't seem to have permissions to re-open, so I hope someone sees this and does so. |
What if you name your show |
I removed the |
Is there any chance you upload your db somewhere, like Dropbox? |
Keeping in mind it's a fresh database every time? Yes, I think so. |
I don't think the database is interesting. It could be the feed or the number of entries. |
Yeah, i missed the part that it's a new db... |
If it helps, I can reproduce it without the actual feed. Here's a sample of 3 that parse and 5 that don't. Notably, these behave the same using the feed or with mock input:
|
can you run a |
@ThubLives Still works for me on Win10 and Ubuntu. |
Still works on my Windows 7 too, with all the latest titles. BTW my Flexget is 2.3.2 |
My Flexget is 2.3.34. locale command:
|
What version of python-dateutil do you have? All of the latest mock entries are parsed and accepted properly on my testing. |
python-dateutil 2.5.2 could be the issue judging by their github and for some reason our requirement is EDIT: Installed 2.5.2 and the issue is reproduced. |
Nice @gazpachoking 👍 |
@liiight he cheated. He's the one who originally made them aware of the bug (dateutil/dateutil#233) |
Ah, I actually remember that now. I take my compliment back cheater! |
Okay, I've updated, but the problem remains. Testing with a fresh database and minimal config with the eight entries above, I still get the same five marked Unknown.
|
After some messing around with pip, it seems I had both python-dateutil 2.5.3 and 2.1 installed somehow. I think I've got 2.5.2 legit now and Flexget is merrily downloading date-style episodes. :) |
Good because our next suggestion would be for you to stop watching that show 😉 |
Expected behaviour:
Recognise ISO-like dates in the format "2016.10.21".
Actual behaviour:
Rejects all shows with date ID's.
Steps to reproduce:
Config:
Log:
Additional information:
The text was updated successfully, but these errors were encountered: