-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Hierarchical partition tests #24848
Closed
v1k1
wants to merge
179
commits into
Azure:hierarchical-partition
from
v1k1:hierarchical-partition-tests
Closed
Hierarchical partition tests #24848
v1k1
wants to merge
179
commits into
Azure:hierarchical-partition
from
v1k1:hierarchical-partition-tests
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
* delte key value in recording in search * update files * update files * Update uriSanitizer and bodySanitizer Co-authored-by: Mary Gao <yanmeigao1210@gmail.com>
Co-authored-by: Sima Zhu <sizhu@microsoft.com>
* servicenetworking release * update files * update files * update file
) * Browse APIs for Azure Communication Services Phone Numbers. * Fix lint errors. * Fix lint. * Add accept-language to the request headers. * Fix formatting * Update communication-phonenumbers.api.md * Fix formatting * Update ACS phone numbers with tracing client. * Lint fix * Fix merge conflict. * Rename AreCodeResult to AreaCodeItem * Add administrativeDivision into ListLocalitiesOptions * Add optional parameters into ListOfferingsOptions * Resolve changes from sdk review * Add live tests * Adjust tests to match api fix * Add swagger readme updates * Split tests into different specs * Change swagger file * Replace area codes and localities tests with first locality * Update recordings * Update tests to new recorder * Update recordings * Update recordings with purchase * Fix lint errors * Fix format * Update recordings * Solve PR comments * Fix format in models * Prettier format in models * Build communication * Fix spelling error Co-authored-by: Adrian Tang <adtang@microsoft.com> Co-authored-by: Sofia Robles <sofiar@microsoft.com>
…24409) Post release automated changes for azure-arm-servicenetworking
* Automatic rush update --full * fix format Co-authored-by: Deyaaeldeen Almahallawi <dealmaha@microsoft.com>
Co-authored-by: Konrad Jamrozik <kojamroz@microsoft.com>
### Packages impacted by this PR @azure/core-lro ### Issues associated with this PR N/A ### Describe the problem that is addressed by this PR Some unit tests didn't take the `throwOnNon2xxResponse` flag into account but they should. This PR updates the poller configuration in them to use the flag. The PR also adjusts expectation accordingly, mainly that when running in the non-throwing mode, no thrown error is expected. ### What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen? N/A ### Are there test cases added in this PR? _(If not, why?)_ N/A ### Provide a list of related PRs _(if any)_ ### Command used to generate this PR:**_(Applicable only to SDK release request PRs)_ ### Checklists - [x] Added impacted package name to the issue description - [ ] Does this PR needs any fixes in the SDK Generator?** _(If so, create an Issue in the [Autorest/typescript](https://github.com/Azure/autorest.typescript) repository and link it here)_ - [ ] Added a changelog (if necessary)
…clude version (Azure#23863) * Add a test case for listing with prefix, delimiter and include version * Add support for cold tier
Co-authored-by: Konrad Jamrozik <kojamroz@microsoft.com>
…re#24413) * Update changelog for communication-phone-numbers * Rephrase changelog * Run release preparation script * Add SIP routing client entries to changelog
Post release automated changes for azure-rest-maps-geolocation
After [@azure/msal-node@1.14.6](https://www.npmjs.com/package/@azure/msal-node/v/1.14.6) has been released.
This release contains the work in Azure#24159 and is needed for the code generator tests to pass.
Post release automated changes for azure-core-lro
… Release Lease (Azure#23530) * [Storage]Append with, Acquire, Release & Renewal of Lease; Flush with Release Lease * Add change log description * Resolve comments * Resolve comments
* refresh9 * update files * update files * update files * update files * update files
* containerservice release * update files
…line (Azure#24416) Migrate to coreV2 and new test recorder.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
AgriFood
App Configuration
Azure.ApplicationModel.Configuration
Attestation
Azure.Core
Batch
Cognitive - Translator
Communication
Confidential Ledger
Container Registry
Cosmos
dev-tool
Issues related to the Azure SDK for JS dev-tool
Digital Twins
eslint plugin
Event Grid
Mgmt
This issue is related to a management-plane library.
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.
Packages impacted by this PR
Issues associated with this PR
Describe the problem that is addressed by this PR
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
Are there test cases added in this PR? (If not, why?)
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists