-
Notifications
You must be signed in to change notification settings - Fork 114
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
HAMA Log Improvements #72
Comments
|
@ZeroQI, for number 1 do we want to start storing the media info (series id/ep num/files) into the HAMA data directory? If we do, we can start referencing seriesX file info outside a seriesY update. |
@sven-7: 1) you can delete logs since you run a full update afterwards... Don't see any need for change there |
(3) has been committed |
(2) has been committed |
EX Log statements.
AniDB ID:
|
@EndOfLine369 Nice :D |
Nice!! Will test soon. Thanks! 😬😉🍺 |
I'm not having any of the HAMA htm logs generate now. I've done two full refreshes (with an intentional missing episode) and nothing has popped up. |
Sounds like a problem on your end as neither of my changes touched anything related to the file generation. Only the data in two of them. Please make sure all your Hama files are up-to-date (namely DefaultPrefs.json & init.py). If after updating your files and it still does not run, will need to see your hama log. |
I had not replaced the .json. (I typically only replace the .py) Thanks! Everything is working now! |
A few things on the Logs:
1. AniDB lines seem to be reverse numerical/alphabetical in their lines. TVDB all seem to be fine.
The text was updated successfully, but these errors were encountered: