Merged main back in #504
Merged
Merged main back in #504
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
…entation (Azure#42307) * Add ASP.NET Core and HTTP Client metrics instrumentation * Changelog update * Update .NET 8.0 and above to use built-in meter. * Update readme * readme - swich doc to use new api. * Update sdk/monitor/Azure.Monitor.OpenTelemetry.AspNetCore/README.md * Update sdk/monitor/Azure.Monitor.OpenTelemetry.AspNetCore/README.md * Update CHANGELOG.md * Update CHANGELOG.md * Update CHANGELOG.md * Update CHANGELOG.md * Update sdk/monitor/Azure.Monitor.OpenTelemetry.AspNetCore/README.md Co-authored-by: Rajkumar Rangaraj <rajrang@microsoft.com> * Update README.md * Update README.md * Update sdk/monitor/Azure.Monitor.OpenTelemetry.AspNetCore/CHANGELOG.md Co-authored-by: Vishwesh Bankwar <vishweshbankwar@users.noreply.github.com> * Update README.md * Update README.md * Update README.md * Update OpenTelemetryBuilderExtensions.cs * Update sdk/monitor/Azure.Monitor.OpenTelemetry.AspNetCore/README.md Co-authored-by: Vishwesh Bankwar <vishweshbankwar@users.noreply.github.com> * Update README.md * Update README.md * Update sdk/monitor/Azure.Monitor.OpenTelemetry.AspNetCore/CHANGELOG.md Co-authored-by: Vishwesh Bankwar <vishweshbankwar@users.noreply.github.com> * Update sdk/monitor/Azure.Monitor.OpenTelemetry.AspNetCore/CHANGELOG.md Co-authored-by: Vishwesh Bankwar <vishweshbankwar@users.noreply.github.com> * Update sdk/monitor/Azure.Monitor.OpenTelemetry.AspNetCore/README.md Co-authored-by: Vishwesh Bankwar <vishweshbankwar@users.noreply.github.com> * Update sdk/monitor/Azure.Monitor.OpenTelemetry.AspNetCore/README.md Co-authored-by: Vishwesh Bankwar <vishweshbankwar@users.noreply.github.com> --------- Co-authored-by: Timothy Mothra <tilee@microsoft.com> Co-authored-by: Vishwesh Bankwar <vishweshbankwar@users.noreply.github.com>
* Update Generator Version 3.0.0-beta.20240311.3 * Update SDK codes de_he_2 * Update SDK codes he_mi_3 * Update SDK codes ad_co_0 * Update SDK codes sq_wo_6 * Update SDK codes mi_pu_4 * Update SDK codes co_da_1 * Update SDK codes pu_sq_5 * Fix tests based on new names * fix test * regen * snippets --------- Co-authored-by: Mingzhe Huang <archerzz@users.noreply.github.com> Co-authored-by: jolov <jolov@microsoft.com>
…r api (Azure#42642) * remove SourceCallerIdNumber from answercallOptions, update autorest with new swagger * create internal classes for media feature and ops feature models * update api * add SourceCallIdNumber to Transfer
* prep AspNetCore for release * simplify metrics statement
* Latest swagger * Fixing swagger * Adding Hold/Unhold methods * adding hold/unhold * Maintaining StartHoldMusic backwards compatible * Adding changes to Participants Updated event and HoldFailed * Adding API changes * Fixing merge with new regeneration * Fixing test * Fixing test * Fixing generate errors * Fixing merge
* Fix areacodes pageable bug * Update recordings
…Azure#42671) Co-authored-by: Praveen Kuttappan <prmarott@microsoft.com>
* Prepare for release * fix changelog
…e property (Azure#42692) * Transform Rooms swagger to match customized ParticipantProperties.Role property * Fix comment
…tensions.ServiceBus (Azure#42694)
* Remote Rendering Test Fix * Error message was changed to a more user friendly one in the service. * Updated recordings --------- Co-authored-by: Christopher Manthei <chmant@microsoft.com>
* [TestFramework] Make ClientSecret optional The focus of these changes is to make the ClientSecret and ClientId environment variables optional. This is to support scenarios where using `DefaultAzureCredential` is preferred, such as local runs for live tests.
…ationDiscoverySap (Azure#43183)
* [Template] Remove unused perf and stress folders The focus of these changes is to remove the unused perf and stress folders from the template. The Azure SDK team no long requires performance tests for each library and partner teams do not use the scaffolding when generating a new library. Likewise, the stress folder is empty, save a README, which simply points to a wiki location that our onboarding guide also references. In the interest of streamlining the template to avoid confusion and to keep the size of the repository down, these folders are being removed.
* Use different service connection and az CLI for ACR auth * displayName --------- Co-authored-by: Daniel Jurek <djurek@microsoft.com>
* [Messaging] Allow binary application properties The focus of these changes is to update AMQP conversion to remove the validation that disallows `byte[]` and `ArraySegment<byte>` values in application properties. These are confirmed to be encoded as `binary` by `Microsoft.Azure.Amqp`, making them allowable values according to section 3.2.5 of the AMQP specification. The Event Hubs documentation for `EventData` has been updated to reflect this change. Due to a known bug in the Service Bus service, the service will reject messages with `byte[]` application properties. Until this is confirmed fixed, the Service Bus documentation still reflects `byte[]` as an invalid type for the application properties.
* Update Generator Version 3.0.0-beta.20240404.1 * Update SDK codes he_mi_3 * Update SDK codes de_he_2 * Update SDK codes ad_co_0 * Update SDK codes sq_wo_6 * Update SDK codes mi_pu_4 * Update SDK codes pu_sq_5 * Update SDK codes co_de_1 * Build fix * Build fix Azure#2 * Build fix Azure#3 --------- Co-authored-by: Alexander Sher <alsher@microsoft.com>
…ure#43214) * Preparation for release of Azure.Core.Experimental v0.1.0-beta.33 * add changelog entry for change
…#43212) * Make message.Apply(options) take nullable options * add test coverage
* Prepare for release * bump minor * Add experimental attribute
* Update dependency version * Remove project refs
* Increment package version after release of Azure.Provisioning.AppConfiguration * Increment package version after release of Azure.Provisioning.ApplicationInsights * Increment package version after release of Azure.Provisioning.Storage * Increment package version after release of Azure.Provisioning.Search * Increment package version after release of Azure.Provisioning.CosmosDB * Increment package version after release of Azure.Provisioning.PostgreSql * Increment package version after release of Azure.Provisioning.EventHubs * Increment package version after release of Azure.Provisioning.Redis * Increment package version after release of Azure.Provisioning.Sql * Increment package version after release of Azure.Provisioning.CognitiveServices * Increment package version after release of Azure.Provisioning.ServiceBus * Increment package version after release of Azure.Provisioning.KeyVault * Increment package version after release of Azure.Provisioning.OperationalInsights * Increment package version after release of Azure.Provisioning.SignalR * Increment package version after release of Azure.Provisioning.Resources
* Increment package version after release of System.ClientModel * Increment package version after release of Azure.Core.Experimental
The focus of these changes is to fix a typo causing a test to hang indefinitely. The assertions in this test were causing an exception that prevented the handler from running, which in turn caused the exit condition to never be met.
The focus of these changes is to fix several mistakes related to ETW logs. Some messages that included links to the troubleshooting guide were improperly annotated with `[Event]` instead of `[NonEvent]`, causing ETW to log a warning for "too many parameters" when writing the messages. Also corrected a parameter ordering issue for an event batch processing error, causing the structured argument parameters to be ordered differently than they appear in the message template.
…e for Duration (Azure#43080) * Parse the Duration field from string to TimeSpan to update with Model change * Only convert the fieldExpression if the incoming data field type of the fieldExpression is of type `string`. In other words, the conversion should only happen if Document.Duration field type is `string`. If there are other field type of `TimeSpan`, don't do this conversion. * Add unit tests that checks when Duration field is of type `string`
… DataMovement.Blobs.Test package (Azure#43221) * Moving single transfer blob tests to datamovement blob tests package * Fixed conflicts between Base Blobs and DM Blobs in the same tests package; WIP - assets recordings * Rerecorded tests * Recorded tests after main merge * Rerecord again * Added properties tests in * Removing merge mistake and old tests that were moved to blobs package
|
Thank you for your contribution @thompson-tomo! We will review the pull request and get back to you soon. |
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.
Merged main back in