azure-rest-api-specs icon indicating copy to clipboard operation
azure-rest-api-specs copied to clipboard

Release playwrighttesting microsoft.playwright testing preview/2024 06 01 preview

Open mjmadhu opened this issue 1 year ago • 11 comments

Data Plane API Specification Update Pull Request

[!TIP] Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

PR review workflow diagram

Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

spec_pr_review_workflow_diagram

API Info: The Basics

Most of the information about your service should be captured in the issue that serves as your API Spec engagement record.

  • Link to API Spec engagement record issue:

Is this review for (select one):

  • [ ] a private preview
  • [x] a public preview
  • [ ] GA release

Change Scope

This section will help us focus on the specific parts of your API that are new or have been modified.
Please share a link to the design document for the new APIs, a link to the previous API Spec document (if applicable), and the root paths that have been updated.

  • Design Document:
  • Previous API Spec Doc:
  • Updated paths:

Viewing API changes

For convenient view of the API changes made by this PR, refer to the URLs provided in the table in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures

If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the Swagger-Suppression-Process to get approval.

❔Got questions? Need additional info?? We are here to help!

Contact us!

The Azure API Review Board is dedicated to helping you create amazing APIs. You can read about our mission and learn more about our process on our wiki.

Click here for links to tools, specs, guidelines & other good stuff

Tooling

Guidelines & Specifications

Helpful Links

Getting help

  • First, please carefully read through this PR description, from top to bottom.
  • If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
  • To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
  • For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure and https://aka.ms/ci-fix.
  • If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run. This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
  • If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

mjmadhu avatar May 29 '24 09:05 mjmadhu

Next Steps to Merge

Next steps that must be taken to merge this PR:
  • ❌ This is the public specs repo main branch which is not intended for iterative development.
    You must acknowledge that you understand that after this PR is merged, you won't be able to stop your changes from being published to Azure customers.
    If this is what you intend, add PublishToCustomers label to your PR.
    Otherwise, retarget this PR onto a feature branch, i.e. with prefix release- (see aka.ms/azsdk/api-versions#release--branches).
  • ❌ Your PR requires an API stewardship board review as it introduces a new API version (label: new-api-version). Schedule the review by following aka.ms/azsdk/onboarding/restapischedule.
  • ❌ The required check named TypeSpec Validation has failed. Refer to the check in the PR's 'Checks' tab for details on how to fix it and consult the aka.ms/ci-fix guide

Swagger Validation Report

️️✔️BreakingChange succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️Breaking Change(Cross-Version) succeeded [Detail] The following breaking changes are detected by comparison with the latest preview version:
Rule Message
Runtime Exception "new":"https://github.com/Azure/azure-rest-api-specs/blob/a79cdc655456382a890913f7c252ac2fdfbc9d2b/specification/playwrighttesting/data-plane/Microsoft.PlaywrightTesting.AuthManager/preview/2024-06-01-preview/playwrighttesting.json",
"old":"https://github.com/Azure/azure-rest-api-specs/blob/main/specification/playwrighttesting/data-plane/Microsoft.PlaywrightTesting.AuthManager/preview/2023-10-01-preview/playwrighttesting.json",
"details":"Breaking change detector (OAD) invoked AutoRest. AutoRest threw a runtime error. First 20 lines of stack trace follow,
indexed. First line should contain AutoRest command line invocation details. Remaining lines should contain the main message reported by AutoRest.
====================
1: Command failed: node "/mnt/vss/_work/_tasks/AzureApiValidation_5654d05d-82c1-48da-ad8f-161b817f6d41/0.0.110/common/temp/node_modules/.pnpm/@[email protected]/node_modules/autorest/dist/app.js" --v2 --input-file=specification/playwrighttesting/data-plane/Microsoft.PlaywrightTesting.AuthManager/preview/2024-06-01-preview/playwrighttesting.json --output-artifact=swagger-document.json --output-artifact=swagger-document.map --output-file=new --output-folder=/tmp/oad-fXzXp1
2: ERROR: Schema violation: Data does not match any schemas from 'oneOf'
3:
4: code: 'ONE-OF-MISSING',

5: params: [],

6: message: "Data does not match any schemas from 'oneOf'",

7: path: '#/paths/~1accounts~1accountId~1browsers/get/x-ms-examples/Accounts-GetBrowsers',

8: schemaId: 'https://raw.githubusercontent.com/Azure/autorest/master/schema/swagger-extensions.json#',

9: inner: [
10:
11: code: 'PATTERN',

12: params: [
13: '^(http
️️✔️CredScan succeeded [Detail] [Expand]
There is no credential detected.
️❌LintDiff: 1 Errors, 13 Warnings failed [Detail]
Compared specs (v2.2.2) new version base version
package-2024-06-01-preview package-2024-06-01-preview(a79cdc6) default(main)

[must fix]The following errors/warnings are introduced by current PR:

Rule Message Related RPC [For API reviewers]
ValidResponseCodeRequired There is no declared valid status code.
Location: Microsoft.PlaywrightTesting.AuthManager/preview/2024-06-01-preview/playwrighttesting.json#L464
:warning: SecurityDefinitionDescription Security definition should have a description.
Location: Microsoft.PlaywrightTesting.AuthManager/preview/2024-06-01-preview/playwrighttesting.json#L42
:warning: PathParameterSchema Path parameter should specify a maximum length (maxLength) and characters allowed (pattern).
Location: Microsoft.PlaywrightTesting.AuthManager/preview/2024-06-01-preview/playwrighttesting.json#L61
:warning: PathParameterSchema Path parameter should specify a maximum length (maxLength) and characters allowed (pattern).
Location: Microsoft.PlaywrightTesting.AuthManager/preview/2024-06-01-preview/playwrighttesting.json#L114
:warning: PathParameterSchema Path parameter should specify a maximum length (maxLength) and characters allowed (pattern).
Location: Microsoft.PlaywrightTesting.AuthManager/preview/2024-06-01-preview/playwrighttesting.json#L170
:warning: PathParameterSchema Path parameter should specify a maximum length (maxLength) and characters allowed (pattern).
Location: Microsoft.PlaywrightTesting.AuthManager/preview/2024-06-01-preview/playwrighttesting.json#L177
:warning: OperationId OperationId for put method should contain both 'Create' and 'Update'
Location: Microsoft.PlaywrightTesting.AuthManager/preview/2024-06-01-preview/playwrighttesting.json#L223
:warning: PathParameterSchema Path parameter should specify a maximum length (maxLength) and characters allowed (pattern).
Location: Microsoft.PlaywrightTesting.AuthManager/preview/2024-06-01-preview/playwrighttesting.json#L229
:warning: PathParameterSchema Path parameter should specify a maximum length (maxLength) and characters allowed (pattern).
Location: Microsoft.PlaywrightTesting.AuthManager/preview/2024-06-01-preview/playwrighttesting.json#L236
:warning: PathParameterSchema Path parameter should specify a maximum length (maxLength) and characters allowed (pattern).
Location: Microsoft.PlaywrightTesting.AuthManager/preview/2024-06-01-preview/playwrighttesting.json#L310
:warning: PathParameterSchema Path parameter should specify a maximum length (maxLength) and characters allowed (pattern).
Location: Microsoft.PlaywrightTesting.AuthManager/preview/2024-06-01-preview/playwrighttesting.json#L317
:warning: PathParameterSchema Path parameter should specify a maximum length (maxLength) and characters allowed (pattern).
Location: Microsoft.PlaywrightTesting.AuthManager/preview/2024-06-01-preview/playwrighttesting.json#L368
:warning: SuccessResponseBody All success responses except 202 & 204 should define a response body.
Location: Microsoft.PlaywrightTesting.AuthManager/preview/2024-06-01-preview/playwrighttesting.json#L380
:warning: PathParameterSchema Path parameter should specify a maximum length (maxLength) and characters allowed (pattern).
Location: Microsoft.PlaywrightTesting.AuthManager/preview/2024-06-01-preview/playwrighttesting.json#L453
️️✔️Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️SwaggerAPIView succeeded [Detail] [Expand]
️️✔️TypeSpecAPIView succeeded [Detail] [Expand]
️️✔️ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️PoliCheck succeeded [Detail] [Expand]
Validation passed for PoliCheck.
️️✔️SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️Lint(RPaaS) succeeded [Detail] [Expand]
Validation passes for Lint(RPaaS).
️️✔️PR Summary succeeded [Detail] [Expand]
Validation passes for Summary.
️️✔️Automated merging requirements met succeeded [Detail] [Expand]
Posted by Swagger Pipeline | How to fix these errors?

Swagger Generation Artifacts

️️✔️ApiDocPreview succeeded [Detail] [Expand]
 Please click here to preview with your @microsoft account. 
️⚠️ azure-sdk-for-js warning [Detail]
    For more instructions, please refer to the FAQ .
  • ⚠️Warning in generating from a69280699e5893f75a6bc98ca4eeea373132477d. SDK Automation 14.0.0
    command	sh .scripts/automation_init.sh ../azure-sdk-for-js_tmp/initInput.json ../azure-sdk-for-js_tmp/initOutput.json
    warn	Warning: File azure-sdk-for-js_tmp/initOutput.json not found to read. Please re-run the pipeline if the error is transitient error or report this issue through https://aka.ms/azsdk/support/specreview-channel.
    command	sh .scripts/automation_generate.sh ../azure-sdk-for-js_tmp/generateInput.json ../azure-sdk-for-js_tmp/generateOutput.json
    warn	Warning: No file changes detected after the generation. Please refer to the generation errors to understand the reasons.
    warn	Warning: No package detected after generation. Please refer to the above logs to understand why the package hasn't been generated.
  • ️✔️@azure-rest/microsoft-playwright-testing [Preview SDK Changes]
    info	[Changelog]
    error	breakingChangeTracking is enabled, but version or changelogItem is not found in output.
️🔄 azure-sdk-for-python inProgress [Detail]
️⚠️ azure-sdk-for-java warning [Detail]
    For more instructions, please refer to the FAQ .
  • ⚠️Warning in generating from a69280699e5893f75a6bc98ca4eeea373132477d. SDK Automation 14.0.0
    command	./eng/mgmt/automation/init.sh ../azure-sdk-for-java_tmp/initInput.json ../azure-sdk-for-java_tmp/initOutput.json
    command	./eng/mgmt/automation/generate.py ../azure-sdk-for-java_tmp/generateInput.json ../azure-sdk-for-java_tmp/generateOutput.json
    warn	Warning: No file changes detected after the generation. Please refer to the generation errors to understand the reasons.
    warn	Warning: No package detected after generation. Please refer to the above logs to understand why the package hasn't been generated.
  • ️✔️azure-developer-microsoftplaywrighttesting [Preview SDK Changes]
️❌ azure-sdk-for-net-track2 failed [Detail]
    For more instructions, please refer to the FAQ .
  • Pipeline Framework Failed in generating from a69280699e5893f75a6bc98ca4eeea373132477d. SDK Automation 14.0.0
    command	pwsh ./eng/scripts/Automation-Sdk-Init.ps1 ../azure-sdk-for-net_tmp/initInput.json ../azure-sdk-for-net_tmp/initOutput.json
    command	pwsh ./eng/scripts/Invoke-GenerateAndBuildV2.ps1 ../azure-sdk-for-net_tmp/generateInput.json ../azure-sdk-for-net_tmp/generateOutput.json
    cmderr	[Invoke-GenerateAndBuildV2.ps1] npm notice
    cmderr	[Invoke-GenerateAndBuildV2.ps1] npm notice New minor version of npm available! 10.7.0 -> 10.8.1
    cmderr	[Invoke-GenerateAndBuildV2.ps1] npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.8.1
    cmderr	[Invoke-GenerateAndBuildV2.ps1] npm notice To update run: npm install -g [email protected]
    cmderr	[Invoke-GenerateAndBuildV2.ps1] npm notice
    cmderr	[Invoke-GenerateAndBuildV2.ps1] GeneratePackage: /mnt/vss/_work/1/s/azure-sdk-for-net/eng/scripts/Invoke-GenerateAndBuildV2.ps1:144
    cmderr	[Invoke-GenerateAndBuildV2.ps1] Line |
    cmderr	[Invoke-GenerateAndBuildV2.ps1]  144 |              GeneratePackage `
    cmderr	[Invoke-GenerateAndBuildV2.ps1]      |              ~~~~~~~~~~~~~~~~~
    cmderr	[Invoke-GenerateAndBuildV2.ps1]      | Failed to build project. exit code: False
    error	FatalError: ConfigError: Invalid GenerateOutput: .packages[0].installInstructions should be object. Please refer to the schema definitions at https://github.com/Azure/azure-rest-api-specs/tree/main/documentation/sdkautomation to fix the configuration issue.. Please refer to the inner logs for details or report this issue through https://aka.ms/azsdk/support/specreview-channel.
    ConfigError: Invalid GenerateOutput: .packages[0].installInstructions should be object. Please refer to the schema definitions at https://github.com/Azure/azure-rest-api-specs/tree/main/documentation/sdkautomation to fix the configuration issue.
    error	ErrorStack: Error: ConfigError: Invalid GenerateOutput: .packages[0].installInstructions should be object. Please refer to the schema definitions at https://github.com/Azure/azure-rest-api-specs/tree/main/documentation/sdkautomation to fix the configuration issue.    at /mnt/vss/_work/1/a/unified-pipeline-runtime/private/openapi-sdk-automation/lib/types/validator.js:32:19    at workflowCallGenerateScript (/mnt/vss/_work/1/a/unified-pipeline-runtime/private/openapi-sdk-automation/lib/automation/workflow.js:605:69)    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)    at async workflowHandleReadmeMdOrTypeSpecProject (/mnt/vss/_work/1/a/unified-pipeline-runtime/private/openapi-sdk-automation/lib/automation/workflow.js:239:40)    at async workflowMain (/mnt/vss/_work/1/a/unified-pipeline-runtime/private/openapi-sdk-automation/lib/automation/workflow.js:107:9)    at async sdkAutoMain (/mnt/vss/_work/1/a/unified-pipeline-runtime/private/openapi-sdk-automation/lib/automation/entrypoint.js:199:13)    at async /mnt/vss/_work/1/a/unified-pipeline-runtime/private/openapi-sdk-automation/lib/cli/cli.js:20:18.
Posted by Swagger Pipeline | How to fix these errors?

Swagger Generation Artifacts

️️✔️ApiDocPreview succeeded [Detail] [Expand]
 Please click here to preview with your @microsoft account. 
️⚠️ azure-sdk-for-js warning [Detail]
  • ⚠️Warning in generating from f220119042f742290d6fbe9d269be8533df28402. SDK Automation 14.0.0
    command	sh .scripts/automation_init.sh ../azure-sdk-for-js_tmp/initInput.json ../azure-sdk-for-js_tmp/initOutput.json
    warn	File azure-sdk-for-js_tmp/initOutput.json not found to read
    command	sh .scripts/automation_generate.sh ../azure-sdk-for-js_tmp/generateInput.json ../azure-sdk-for-js_tmp/generateOutput.json
    warn	No file changes detected after generation
    warn	No package detected after generation
️⚠️ azure-sdk-for-python warning [Detail]
  • ⚠️Warning in generating from f220119042f742290d6fbe9d269be8533df28402. SDK Automation 14.0.0
    command	sh scripts/automation_init.sh ../azure-sdk-for-python_tmp/initInput.json ../azure-sdk-for-python_tmp/initOutput.json
    cmderr	[automation_init.sh] W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/azure-cli.list:1 and /etc/apt/sources.list.d/azure-cli.sources:1
    cmderr	[automation_init.sh] W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/azure-cli.list:1 and /etc/apt/sources.list.d/azure-cli.sources:1
    cmderr	[automation_init.sh] W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/azure-cli.list:1 and /etc/apt/sources.list.d/azure-cli.sources:1
    cmderr	[automation_init.sh] W: Target CNF (main/cnf/Commands-amd64) is configured multiple times in /etc/apt/sources.list.d/azure-cli.list:1 and /etc/apt/sources.list.d/azure-cli.sources:1
    cmderr	[automation_init.sh] W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list.d/azure-cli.list:1 and /etc/apt/sources.list.d/azure-cli.sources:1
    cmderr	[automation_init.sh] W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/azure-cli.list:1 and /etc/apt/sources.list.d/azure-cli.sources:1
    cmderr	[automation_init.sh] W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/azure-cli.list:1 and /etc/apt/sources.list.d/azure-cli.sources:1
    cmderr	[automation_init.sh] W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/azure-cli.list:1 and /etc/apt/sources.list.d/azure-cli.sources:1
    cmderr	[automation_init.sh] W: Target CNF (main/cnf/Commands-amd64) is configured multiple times in /etc/apt/sources.list.d/azure-cli.list:1 and /etc/apt/sources.list.d/azure-cli.sources:1
    cmderr	[automation_init.sh] W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list.d/azure-cli.list:1 and /etc/apt/sources.list.d/azure-cli.sources:1
    cmderr	[automation_init.sh] WARNING: Skipping azure-nspkg as it is not installed.
    cmderr	[automation_init.sh] npm notice
    cmderr	[automation_init.sh] npm notice New minor version of npm available! 10.7.0 -> 10.8.1
    cmderr	[automation_init.sh] npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.8.1
    cmderr	[automation_init.sh] npm notice To update run: npm install -g [email protected]
    cmderr	[automation_init.sh] npm notice
    warn		specification/playwrighttesting/PlaywrightTesting/tspconfig.yaml skipped due to azure-sdk-for-python not found in tspconfig.yaml
    command	sh scripts/automation_generate.sh ../azure-sdk-for-python_tmp/generateInput.json ../azure-sdk-for-python_tmp/generateOutput.json
    warn	No file changes detected after generation
    warn	No package detected after generation
️🔄 azure-sdk-for-java inProgress [Detail]
️🔄 azure-sdk-for-net-track2 inProgress [Detail]
Posted by Swagger Pipeline | How to fix these errors?

Swagger Validation Report

️️✔️BreakingChange succeeded [Detail] [Expand]
There are no breaking changes.
️⚠️Breaking Change(Cross-Version): 7 Warnings warning [Detail]
Compared specs (v0.10.9) new version base version
playwrighttesting.json 2024-06-01-preview(4fe6d4d) 2023-10-01-preview(main)

The following breaking changes are detected by comparison with the latest preview version:

Rule Message
:warning: 1025 - RequiredStatusChange The 'required' status changed from the old version('False') to the new version('True').
New: Microsoft.PlaywrightTesting.AuthManager/preview/2024-06-01-preview/playwrighttesting.json#L482:7
Old: Microsoft.PlaywrightTesting.AuthManager/preview/2023-10-01-preview/playwrighttesting.json#L353:7
:warning: 1034 - AddedRequiredProperty The new version has new required property 'createdAt, state' that was not found in the old version.
New: Microsoft.PlaywrightTesting.AuthManager/preview/2024-06-01-preview/playwrighttesting.json#L788:11
Old: Microsoft.PlaywrightTesting.AuthManager/preview/2023-10-01-preview/playwrighttesting.json#L657:11
:warning: 1034 - AddedRequiredProperty The new version has new required property 'createdAt, state' that was not found in the old version.
New: Microsoft.PlaywrightTesting.AuthManager/preview/2024-06-01-preview/playwrighttesting.json#L191:13
Old: Microsoft.PlaywrightTesting.AuthManager/preview/2023-10-01-preview/playwrighttesting.json#L180:13
:warning: 1034 - AddedRequiredProperty The new version has new required property 'createdAt, state' that was not found in the old version.
New: Microsoft.PlaywrightTesting.AuthManager/preview/2024-06-01-preview/playwrighttesting.json#L251:13
Old: Microsoft.PlaywrightTesting.AuthManager/preview/2023-10-01-preview/playwrighttesting.json#L240:13
:warning: 1034 - AddedRequiredProperty The new version has new required property 'createdAt, state' that was not found in the old version.
New: Microsoft.PlaywrightTesting.AuthManager/preview/2024-06-01-preview/playwrighttesting.json#L259:13
Old: Microsoft.PlaywrightTesting.AuthManager/preview/2023-10-01-preview/playwrighttesting.json#L248:13
:warning: 1034 - AddedRequiredProperty The new version has new required property 'createdAt, state' that was not found in the old version.
New: Microsoft.PlaywrightTesting.AuthManager/preview/2024-06-01-preview/playwrighttesting.json#L272:13
Old: Microsoft.PlaywrightTesting.AuthManager/preview/2023-10-01-preview/playwrighttesting.json#L261:13
:warning: 1034 - AddedRequiredProperty The new version has new required property 'createdAt, state' that was not found in the old version.
New: Microsoft.PlaywrightTesting.AuthManager/preview/2024-06-01-preview/playwrighttesting.json#L479:5
Old: Microsoft.PlaywrightTesting.AuthManager/preview/2023-10-01-preview/playwrighttesting.json#L350:5
️️✔️CredScan succeeded [Detail] [Expand]
There is no credential detected.
️❌LintDiff: 4 Errors, 0 Warnings failed [Detail] [must fix]The following errors/warnings are introduced by current PR:
Rule Message Related RPC [For API reviewers]
AutoRest exception "tag":"package-2024-06-01-preview",
"details":"[OperationAbortedException] Error occurred. Exiting."
AutoRest exception "tag":"package-2024-06-01-preview",
"details":"!Error: [OperationAbortedException] Error occurred. Exiting."
AutoRest exception "tag":"package-2024-06-01-preview",
"details":"Autorest completed with an error. If you think the error message is unclear,
or is a bug,
please declare an issues at https://github.com/Azure/autorest/issues with the error message you are seeing."
AutoRest exception "tag":"package-2024-06-01-preview",
"details":"Expected a string but got object: [ [ 'Title' ] ]"
️️✔️Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️SwaggerAPIView succeeded [Detail] [Expand]
️️✔️TypeSpecAPIView succeeded [Detail] [Expand]
️️✔️ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️PoliCheck succeeded [Detail] [Expand]
Validation passed for PoliCheck.
️️✔️SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️Lint(RPaaS) succeeded [Detail] [Expand]
Validation passes for Lint(RPaaS).
️️✔️PR Summary succeeded [Detail] [Expand]
Validation passes for Summary.
️️✔️Automated merging requirements met succeeded [Detail] [Expand]
Posted by Swagger Pipeline | How to fix these errors?

I've removed enable-sync-stack from Java tspconfig. This option should only be used in very rare case.

weidongxu-microsoft avatar Jul 01 '24 02:07 weidongxu-microsoft

/azp run

weidongxu-microsoft avatar Jul 01 '24 07:07 weidongxu-microsoft

Azure Pipelines successfully started running 3 pipeline(s).

azure-pipelines[bot] avatar Jul 01 '24 07:07 azure-pipelines[bot]

/azp run

MaryGao avatar Jul 01 '24 08:07 MaryGao

Azure Pipelines successfully started running 3 pipeline(s).

azure-pipelines[bot] avatar Jul 01 '24 08:07 azure-pipelines[bot]

Hi, @mjmadhu. Your PR has no update for 14 days and it is marked as stale PR. If no further update for over 14 days, the bot will close the PR. If you want to refresh the PR, please remove no-recent-activity label.

Hi, @mjmadhu. The PR will be closed since the PR has no update for 28 days. If you still need the PR review to proceed, please reopen it and @ mention PR assignee.