You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have the feeling logging is not working properly. It only logs WARN and ERROR levels, even if I change the level in the configuration (via source code or configuration file).
From what I have seen
first we read the configuration (we import utils.py from main.py and that calls loadConfig)
then we initialize the logging configuration (via setupLogging())
but while we are reading the configuration there is a logging.info statement that already initializes the logging configuration. So this nullify the effect of setupLogging().
Now.
setupLogging() tries to read the configuration (to set the desired level)
but (as I said earlier) reading the configuration already initializes the logging module
So I believe this is an undesired "circular" dependency: logging requires configuration, but configuration initializes logging.
The text was updated successfully, but these errors were encountered:
Before submitting a bug report...
This bug wasn't already reported.
(I have checked every bug report on GitHub)
I've cleared the sessions folder.
Branch
develop
Commit
245d3b1
Describe the bug
I have the feeling logging is not working properly. It only logs WARN and ERROR levels, even if I change the level in the configuration (via source code or configuration file).
From what I have seen
utils.py
frommain.py
and that callsloadConfig
)setupLogging()
)logging.info
statement that already initializes the logging configuration. So this nullify the effect ofsetupLogging()
.Now.
setupLogging()
tries to read the configuration (to set the desired level)So I believe this is an undesired "circular" dependency: logging requires configuration, but configuration initializes logging.
The text was updated successfully, but these errors were encountered: