Closed keppo070 closed 11 months ago
favorited_behavior_movie=['keep', 'any', 'ignore', 3]
Hey, please attach your config. I am not able to reproduce this on my end.
Got it! I wasn't making the correct assumption about your created_filter_movie
config option. Once I change it to match yours I was able to reproduce.
Try with latest v4 trunk v4.1.20; issue should be fixed. Let me know if it is not.
Thnx for the quick fix.
For some reason it seems this issued returned. I removed 1 user from the config file. I'm running single user now.
Again the script is trying te remove "The Professional". Taste differ off course but why does the script hates this movie that it will remove it....
While playing with the options I noticed that Console Outputs is CaseSensitive and I noticed that the debug.log is removed when debug=0 (could be on purpose off course)
MUMC Version: 4.1.20
Emby Version: 4.7.11.0
Python Version: 3.9.2
Time Stamp: 20230513221159
:[KEEPING] - Movie - The Professional - Cerito Films - Unplayed - Play Count: 0 - Created 460 days ago - Favorite: True - WhiteTag: False - BlackTag: False - Whitelisted: False - Blacklisted: True - MovieID: 20565
[DELETED] Movie - The Professional - 20565
Lol, I am not sure why the script hates this movie. More likely something I did wrong. :D
While playing with the options I noticed that Console Outputs is CaseSensitive
I do not understand what you mean by the console is case-sensitive.
I noticed that the debug.log is removed when debug=0 (could be on purpose off course)
Yep. This is by design. Debug file is deleted every time the script runs. When DEBUG
>= 1 it is recreated. When DEBUG=0
it is not recreated. The debug file can be large. No reason to keep it around when debug is disabled.
I meant that the True and False are case-sensitive in the section "Enable/Disable console outputs by type" not a real issue. I just got an error when I used true instead of True
Ahhh yes. That is because Python requires True/False
as Boolean values. I'm just passing the True/False
directly to Python without manipulation.
Are you able to share the mumc_DEBUG.log
? That way I can see what is happening.
I should clarify. Set DEBUG=4
If you are not able to share the mumc_DEBUG.log
I will at least need to see your mumc_config.py
so I can try to reproduce on my end.
I'm trying to get my test environment working. I am not so comfortable to share the entire db inside the log.
My config is the same as in https://github.com/terrelsa13/MUMC/issues/74#issuecomment-1455155938 but now only 1 user. Just me.
@keppo070 Think I found the issue. Working on the fix.
@keppo070
I have not forgotten about this. Long story short the Played Conditional
portion of the script was only taking into account all
, any
, and ignore
for monitored users meeting the played_filter
. Your issue uncovered the script also needs to give options to account for monitored users meeting the played_filter
and/or created_played_filter
. Below are the new options that will be added for Played_Conditional
for all behaviors.
# Played Conditional (Y): Specify how monitored users must meet the played_filter_* and/or created_filter_*.
# all - Every monitored user(s) must meet the Played Count and Played Count Inequality of both the played_filter_* and created_filter_*
# any - One or more monitored user(s) must meet the Played Count and Played Count Inequality of either the played_filter_* or created_filter_*
# all_any - Every monitored user(s) must meet the Played Count and Played Count Inequality of either the played_filter_* or created_filter_*
# any_all - One or more monitored user(s) must meet the Played Count and Played Count Inequality of both the played_filter_* and created_filter_*
# all_played - Every monitored user(s) must meet the Played Count and Played Count Inequality of the played_filter_*
# any_played - One or more monitored user(s) must meet the Played Count and Played Count Inequality of the played_filter_*
# all_created - Every monitored user(s) must meet the Played Count and Played Count Inequality of the created_filter_*
# any_created - One or more monitored user(s) must meet the Played Count and Played Count Inequality of the created_filter_*
# ignore - Ignore if monitored user(s) meet the Played Count and Played Count Inequality of both the played_filter_* and created_filter_*
Because this change has been so extensive I have also taken it as an opportunity to break the single large script into modules. There are also other feature requests and general improvements I am making as well. Apologies for it taking such a long time. I still have a few more feature requests to figure out how to implement; followed by testing. I wish I could give you an ETA, but between life and work I am making changes here and there as fast as I can.
@keppo070 v5 of this script on the beta branch is ~85% complete. It has the additional played conditional options mentioned above.
The config is moving from the legacy format to a yaml format for v5. There is a legacy to yaml converter that should convert the existing config to the new yaml format. But I have only run it on my config. If you are looking to try v5 I suggest copying your current mumc directory so you can go back to it.
There are also a few other items like the config editor and various documentation that are still WIP.
Long story short; YMMV w/ v5
FirstUser
SecondUser
Result