fix: Remove LOGGER.exception() line #1087
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
product-auto-label
bot
added
size: xs
mukund-ananthu
changed the title
|
🤖 I detect that the PR title and the commit message differ and there's only one commit. To use the PR title for the commit history, you can use Github's automerge feature with squashing, or use -- conventional-commit-lint bot |
Information logged in this line will be available to the calling code via the exception thrown. There are scenarios where due to concurrency issues, there are two uncoordinated outputs happening at once. This may result in this line logging stack traces after log statements in the exception block of the calling code.
mukund-ananthu
force-pushed
the
removeLog
branch
from
792f86e to
db683d0
Compare
pradn
approved these changes
Feb 22, 2024
mukund-ananthu
added
the
kokoro:force-run
yoshi-kokoro
removed
the
kokoro:force-run
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.
Information logged in this line will be available to the calling code via the exception thrown.
There are scenarios where due to concurrency issues, there are two uncoordinated outputs happening at once. This may result in this line logging stack traces after log statements in the exception block of the calling code.
Fixes #1086 🦕