The current variable naming was overriding this lock, leading to deadlocks that would occur when the logging framework would attempt to acquire the base handler lock for configuration purposes, which would then cause any attempts by the logdna handler to acquire this lock to block indefinitely.
This PR addresses this issue by renaming the internal lock variable, ensuring that it remains logically distinct as it was intended.
The base
logging.Handlerclass has it's own instance variable namedself.lock. This variable is used to lock access to a given handler.The current variable naming was overriding this lock, leading to deadlocks that would occur when the logging framework would attempt to acquire the base handler lock for configuration purposes, which would then cause any attempts by the logdna handler to acquire this lock to block indefinitely.
This PR addresses this issue by renaming the internal lock variable, ensuring that it remains logically distinct as it was intended.