fix: call to logger with odd number of key/value params #4478
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.
Closes #4193
What changed?
Fix bug with odd number of key/value pairs sent to logger. There is already an open PR to fix this, but we got no response from the author: #4193.
I am also adding a linter to avoid this from happening again: https://github.com/timonwong/loggercheck
Without fixing the bug, but enabling the new linter, it fails:
Why was this change made?
Bugfix to avoid panic if attempting to log from here..
How was this change implemented?
How did you validate the change?
Release notes
Documentation Changes