Repository navigation
Conversation
Imaginary now always logs on info level so that it is visible what it does. Debug output is still additionally enabled if AIO_LOG_LEVEL is set to debug. Assisted-by: ClaudeCode:claude-opus-5-5 Signed-off-by: Simon L. <szaimen@e.mail.de>
pabzm
left a comment
There was a problem hiding this comment.
With this change there's no way anymore for users to make imaginary be quieter, right?
Is that on purpose?
I'd prefer to keep AIO_LOG_LEVEL determining all application's log levels, and not to introduce exceptions, because they increase complexity.
At least unless there's a grave reason for the change. Just for seeing what the apps do, users could set well set AIO_LOG_LEVEL to info, or not?
|
We discussed verbally that we want to introduce this exception because imaginary does not log anything (if there's no problem) with a log level above 'info', which we consider easily irritating for users. |
pabzm
left a comment
There was a problem hiding this comment.
I think the log should contain a note if the log level is 'warn' or 'error', that it gets ignored (like in the watchtower PR).
Signed-off-by: Simon L. <szaimen@e.mail.de>
Done |
Imaginary now always logs on info level so that it is visible what it does. Debug output is still additionally enabled if AIO_LOG_LEVEL is set to debug.
Summary
3. to review, feature component)AI (if applicable)