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

Fixing utils.py #38624

Conversation

FabianMeiswinkel
Copy link
Member

Description

Please add an informative description that covers that changes made by the pull request and link all relevant issues.

If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.

All SDK Contribution checklist:

  • The pull request does not introduce [breaking changes]
  • CHANGELOG is updated for new features, bug fixes or other significant changes.
  • I have read the contribution guidelines.

General Guidelines and Best Practices

  • Title of the pull request is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

  • Pull request includes test coverage for the included changes.

FabianMeiswinkel and others added 12 commits February 3, 2024 01:35
* Check for actual meterRegistry

* Update ClientTelemetryMetrics.java

* Update ClientTelemetryMetrics.java

* Update CosmosDiagnosticsTest.java

* Removing String.format in metrics

* Update ClientTelemetryMetrics.java

* Update Uri.java

* Update RntbdClientChannelHealthChecker.java

* Update RntbdToken.java

* Update FaultInjectionRequestContext.java

* Update RntbdTokenStream.java

* Update RntbdTokenStream.java

* Update RntbdTokenStream.java

* EnumMap changes

* Avoiding ImmutableEnumMaps

* Fixing unit tests

* Update ClientTelemetryMetrics.java

* Update FaultInjectionRequestContext.java
…m property or environment variable (Azure#38388)

* Allowing to opt-out of E2E timeout for non-point operations via system property or environment variable

* Tests

* Reacting to code review feedback
Co-authored-by: annie-mac <xinlian@microsoft.com>
…38416)

* add channelAcquisitionContext in cosmosDiagnostics when reaching threshold

---------

Co-authored-by: annie-mac <xinlian@microsoft.com>
@FabianMeiswinkel FabianMeiswinkel merged commit d9ff0dc into Azure:hotfix/kuthapar/azure-cosmos_4.53.2-hotfix Feb 4, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants