Optimize logger lines containing string formatting #385
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
Akasurde
approved these changes
Jun 3, 2022
Shrews
added a commit
to Shrews/ansible-builder
that referenced
this pull request
Jun 3, 2022
(cherry picked from commit f92a3c9)
eqrx
pushed a commit
that referenced
this pull request
Jun 6, 2022
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.
Use of any formatting other than %-style formatting in logging messages should be avoided. If a logging message will not be logged, you waste cycles formatting the string that will just be thrown away. Using %-style lets the logging library decide when to format.
For reference: