Fix variable name in log record; complement to #11879 #11908
Merged
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
|
test this please |
|
Jenkins results:
|
|
Apologies for bypassing the review, but I wanted to have it in the production deployment in 1h from now. |
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.
Fixes #11620
Complement to #11879
Status
ready
Description
Dennis fixed this issue in this PR: #11905
but I would like to deploy it in production in the upgraded scheduled for today, so here goes a simple fix to the variable name being referenced in an important log record of the WorkQueue.
Is it backward compatible (if not, which system it affects?)
YES
Related PRs
Bug fix for #11879
External dependencies / deployment changes
None