make verbose job logging configurable but disable it by default #170
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mnapoli
reviewed
Feb 7, 2025
|
@mnapoli is there anything, I need to do about the failing spell check action? It doesn't seem to be related to my change, but if it blocks this PR I can try to fix it. |
mnapoli
reviewed
Feb 12, 2025
mnapoli
reviewed
Feb 12, 2025
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR disables verbose logging about every job execution but, as proposed in #146. The verbose logging can still be enabled with the
bref.jobs_logsconfiguration.A logging of every single job execution does not provide any meaningful information, but rather renders logs useless, decreases performance and increases log storage costs.