Well, I'd like to see a fresh
debug log (wiki) with that extra logging enabled to make a final determination, but what I can say from the original debug log is that it is not the lightimdb ratings update addon that keeps updating the db, but something to do with Kodi core. I can say this with certainty because the addon is running in a
different thread to the thread doing the updates.
In the debug log, the thread ID for the addon doing it's stuff is 4243. You can see it starting up in the snippet below.
xml:
2023-02-08 17:51:35.943 T:4243 debug <general>: Thread LanguageInvoker start, auto delete: false
2023-02-08 17:51:35.945 T:4243 debug <general>: initializing python engine.
2023-02-08 17:51:35.946 T:4243 debug <general>: CPythonInvoker(7, /storage/.kodi/addons/script.light.imdb.ratings.update/context.py): start processing
2023-02-08 17:51:37.237 T:4217 debug <general>: connect replacing configured host 192.168.1.119 with resolved host 192.168.1.119
2023-02-08 17:51:37.247 T:4243 debug <general>: -->Python Interpreter Initialized<--
2023-02-08 17:51:37.247 T:4243 debug <general>:
2023-02-08 17:51:37.247 T:4243 debug <general>: CPythonInvoker(7, /storage/.kodi/addons/script.light.imdb.ratings.update/context.py): the source file to load is "/storage/.kodi/addons/script.light.imdb.ratings.update/context.py"
2023-02-08 17:51:37.247 T:4243 debug <general>: CPythonInvoker(7): default python path:
Notice that also in that snippet, Kodi prints a message regarding replacing the configured host with the resolved host. This is a core operation and the thread ID is 4217.
Later on part of the log looks like this
xml:
2023-02-08 17:51:45.971 T:4217 debug <general>: connect replacing configured host 192.168.1.119 with resolved host 192.168.1.119
2023-02-08 17:51:59.264 T:4217 info <general>: Skipped 5 duplicate messages..
2023-02-08 17:51:59.264 T:4217 debug <general>: connect replacing configured host 192.168.1.119 with resolved host 192.168.1.119
2023-02-08 17:51:59.784 T:4217 info <general>: Skipped 3 duplicate messages..
2023-02-08 17:51:59.784 T:4217 info <general>: UpdateDetailsForMovie: Starting updates for movie 2612
2023-02-08 17:51:59.785 T:4217 debug <general>: Mysql Start transaction
2023-02-08 17:51:59.785 T:4217 debug <general>: Mysql execute: UPDATE movie SET c00='12 Angry Men',c01='The defense and the prosecution have rested and the jury is filing into the jury room to decide if a young Spanish-American is guilty or innocent of murdering his father. What begins as an open and shut case soon becomes a mini-drama of each of the jurors\' prejudices and preconceptions about the trial, the accused, and each other.',c02='',c03='Life is in their hands. Death is on their minds.',c05='64435',c06='Reginald Rose',c08='<thumb spoof=\"\" cache=\"\" aspect=\"poster\" preview=\"\">https://assets.fanart.tv/fanart/movies/389/movieposter/12-angry-men-60180a6532efb.jpg</thumb><thumb spoof=\"\" , userrating = NULL, premiered = '1957-04-10' where idMovie=2612
2023-02-08 17:51:59.788 T:4217 debug <general>: Mysql commit transaction
2023-02-08 17:51:59.791 T:4217 info <general>: UpdateDetailsForMovie: Finished updates for movie 2612
Looking again at the thread ID, it is 4217 which is clearly a core thread not an addon thread. From the log I can't say what is triggering the updates, but its most definitely
not an addon.
@
Klojum , @
Karellen FYI.
