[Bug]: loglevel
setting does not work on 31.0.0-RC1
#50443
Labels
Milestone
loglevel
setting does not work on 31.0.0-RC1
#50443
Bug description
The logging system does not seem to respect the
loglevel
configured inconfig.php
or through the admin settings, instead the level is alwayswarning
(2). Testing with value 0 in the configuration, I saw some selected few debug messages appear in the log but most of them were missing.I believe that the bug is in the commit 63f3309. Without understanding the entire
Log
module or the context of the said fix, I'm pretty sure that there should be statement$this->nestingLevel--;
in front of this return statement, too:server/lib/private/Log.php
Line 274 in fba7ef9
Or at least adding this line fixed the issue on my system. This also showcases nicely, why it is usually a bad idea to have multiple return statements in a non-trivial function.
Steps to reproduce
loglevel
as 0loglevel
as 4Expected behavior
The
loglevel
configuration should be respected by the logging system.Nextcloud Server version
31
Operating system
None
PHP engine version
None
Web server
None
Database engine version
None
Is this bug present after an update or on a fresh install?
None
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
No response
The text was updated successfully, but these errors were encountered: