Page 1 of 1

New message in debug log for python plugin.

Posted: Thursday 24 February 2022 17:50
by Thorgal789
Hello, just by curiosity, all is working fine, but if I increase the debug level in my python plugin, I have this kind of lines that flood the windows (more than 1 by seconds)

Code: Select all

(ZIGBEE) Releasing lock for 'ZIGBEE'
(ZIGBEE) Acquiring lock for 'ZIGBEE' 
Some know if it's something normal ? If yes, those logs are realy too much talkatives.

The plugin use a permanent connection by websocket.

Re: New message in debug log for python plugin.

Posted: Saturday 26 February 2022 18:05
by Filip
I have the same especially with plugins using Threading. I just tried with the multi-threading example in the domoticz plugin folder, and got the same...
multi.png
multi.png (27.51 KiB) Viewed 883 times

Re: New message in debug log for python plugin.

Posted: Saturday 26 February 2022 21:26
by ferrosk
This is known issue in Domoticz 2022.1. The fix has been released in beta channel and people are testing it, see viewtopic.php?t=38086

Re: New message in debug log for python plugin.

Posted: Sunday 27 February 2022 10:30
by Thorgal789
Ok, thx, will make a try, in my mind the fix was just for compatibility with recent python version.

Re: New message in debug log for python plugin.

Posted: Sunday 27 February 2022 11:37
by waltervl
I also do not think that the change to a Python ABI will modify the log behavior. This should be addressed to @dnpwwo but I think he has higher priorities.

Re: New message in debug log for python plugin.

Posted: Sunday 27 February 2022 13:59
by Thorgal789

Re: New message in debug log for python plugin.

Posted: Monday 28 February 2022 21:13
by ferrosk
waltervl wrote: Sunday 27 February 2022 11:37 I also do not think that the change to a Python ABI will modify the log behavior. This should be addressed to @dnpwwo but I think he has higher priorities.
The changes (i.e. improved inter-thread locking strategy and others) in Python Framework by moving to new Python ABI fixed the cause of those log messages not just logging behavior. You can see in this thread it indeed helped to fix this problem not only for me and my plugin but also for other people using other plugins...