-
Notifications
You must be signed in to change notification settings - Fork 297
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bot database update scripts: Be quiet by default in cron scripts #2016
Labels
Milestone
Comments
ghost
pushed a commit
that referenced
this issue
Aug 11, 2021
This introduces a --verbose flag to the experts which use update functions. The default behaviour now is to *not* print any messages, which makes the update function less noisy when used with cron. Fixes #2016
ghost
pushed a commit
that referenced
this issue
Aug 11, 2021
This introduces a --verbose flag to the experts which use update functions. The default behaviour now is to *not* print any messages, which makes the update function less noisy when used with cron. Fixes #2016
ghost
pushed a commit
that referenced
this issue
Aug 11, 2021
This introduces a --verbose flag to the experts which use update functions. The default behaviour now is to *not* print any messages, which makes the update function less noisy when used with cron. Fixes #2016
in the domain suffix expert, one line was missing (the |
ghost
pushed a commit
that referenced
this issue
Sep 9, 2021
Only print skipped database update message if verbose mode is active fixes #2016
ghost
pushed a commit
that referenced
this issue
Sep 9, 2021
Only print skipped database update message if verbose mode is active fixes #2016
ghost
pushed a commit
that referenced
this issue
Sep 9, 2021
Only print skipped database update message if verbose mode is active fixes #2016
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
0 participants
Currently, the bot database update scripts print this on every call if nothing is done:
I think a good default would be to be quiet by default on the cron runs, e.g. by setting a
--quiet
flag. If the user wants to have verbose information, it can always be turned on.Or: honour the logging level as defined for the bot. With the configuration overhaul, this should now be easier to do on the code-side.
The text was updated successfully, but these errors were encountered: