Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed Inappropriate Logging and String.format Usage #22450

Merged
merged 4 commits into from
Jun 22, 2021

Conversation

alzimmermsft
Copy link
Member

Fixes #22443

This PR fixes a few cases where ClientLogger and String.format are being used inappropriately. Inappropriate usage is string manipulation before passing into the logger or missing/using incorrect placeholders.

Copy link
Member

@vcolin7 vcolin7 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, just had a small question.

Copy link
Member

@kushagraThapar kushagraThapar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @alzimmermsft for fixing these for cosmos

@alzimmermsft alzimmermsft enabled auto-merge (squash) June 22, 2021 20:02
@alzimmermsft alzimmermsft merged commit 23260e7 into Azure:main Jun 22, 2021
@alzimmermsft alzimmermsft deleted the AzCore_FixJacksonLoggingFormat branch June 23, 2021 16:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
App Configuration Azure.ApplicationModel.Configuration Azure.Core azure-core Azure.Identity Client This issue points to a problem in the data-plane of the library. Cosmos Digital Twins Event Hubs KeyVault Search Service Bus
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[BUG] Wrong logging format used in JacksonAdapter
6 participants