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
What Operating System(s) are you seeing this problem on?
Linux (x86-64)
Backend.AI version
main
Describe the bug
Even if I set the log-level to DEBUG in the toml file, the log-level is always overridden by the default value (INFO) from the CLI, resulting in the logging level always being set to INFO regardless of the config file's log-level.
As a result, it is not possible to change the log-level when using commands other than start-server that do not include the --log-level argument.
To Reproduce
Set the logging level to debug in the toml configuration file.
Run a command that does not include the --log-level argument, such as any command other than start-server.
Observe that the logging level is set to INFO instead of DEBUG.
Expected Behavior
The log-level set in the toml file should be respected, and commands that do not include the --log-level argument should use the log-level specified in the toml configuration.
Anything else?
No response
The text was updated successfully, but these errors were encountered:
jopemachine
changed the title
Wrong Implicit log-level overridding when --log-level argument is not provided
Wrong Implicit log level overridding when --log-level argument is not provided
Aug 22, 2024
What Operating System(s) are you seeing this problem on?
Linux (x86-64)
Backend.AI version
main
Describe the bug
Even if I set the
log-level
toDEBUG
in the toml file, thelog-level
is always overridden by the default value (INFO
) from the CLI, resulting in the logging level always being set toINFO
regardless of the config file'slog-level
.As a result, it is not possible to change the
log-level
when using commands other thanstart-server
that do not include the--log-level
argument.To Reproduce
--log-level
argument, such as any command other thanstart-server
.INFO
instead ofDEBUG
.Expected Behavior
The
log-level
set in the toml file should be respected, and commands that do not include the--log-level
argument should use thelog-level
specified in the toml configuration.Anything else?
No response
The text was updated successfully, but these errors were encountered: