Skip to content

Support ad test 1 #3627

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

Open
wants to merge 9 commits into
base: main
Choose a base branch
from
Open

Support ad test 1 #3627

wants to merge 9 commits into from

Conversation

ruowan
Copy link

@ruowan ruowan commented Jan 9, 2023

MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.

Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo. If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.

Changelog

Add a changelog entry for this PR by answering the following questions:

  1. What's the purpose of the update?
    • new service onboarding
    • new API version
    • update existing version for new feature
    • update existing version to fix swagger quality issue in s360
    • Other, please clarify
  2. When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
  3. When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
  4. If updating an existing version, please select the specific language SDKs and CLIs that must be refreshed after the swagger is published.
    • SDK of .NET (need service team to ensure code readiness)
    • SDK of Python
    • SDK of Java
    • SDK of Js
    • SDK of Go
    • PowerShell
    • CLI
    • Terraform
    • No refresh required for updates in this PR

Contribution checklist:

If any further question about AME onboarding or validation tools, please view the FAQ.

ARM API Review Checklist

Applicability: ⚠️

If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

  • Change to data plane APIs
  • Adding new properties
  • All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

  • Check this box if any of the following appy to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review. Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

    • Adding a new service
    • Adding new API(s)
    • Adding a new API version
      -[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.
  • Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

  • If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist

If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

  • Removing API(s) in a stable version
  • Removing properties in a stable version
  • Removing API version(s) in a stable version
  • Updating API in a stable or public preview version with Breaking Change Validation errors
  • Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.

Please follow the link to find more details on PR review process.

@openapi-pipeline-app-test
Copy link

openapi-pipeline-app-test bot commented Jan 9, 2023

Swagger Validation Report

️️✔️BreakingChange succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️Breaking Change(Cross-Version) succeeded [Detail] [Expand]
There are no breaking changes.
️❌LintDiff: 10 Errors, 85 Warnings failed [Detail]
compared tags (via openapi-validator v2.0.0) new version base version
release_1_1 release_1_1(55518ad) default(main)

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

Only 30 items are listed, please refer to log for more details.

Rule Message Related RPC [For API reviewers]
OperationIdNounVerb Per the Noun_Verb convention for Operation Ids, the noun 'Multivariate' should not appear after the underscore. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
Location: AnomalyDetector/stable/v1.1/openapi.json#L70
OperationIdNounVerb Per the Noun_Verb convention for Operation Ids, the noun 'Multivariate' should not appear after the underscore. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
Location: AnomalyDetector/stable/v1.1/openapi.json#L112
OperationIdNounVerb Per the Noun_Verb convention for Operation Ids, the noun 'Multivariate' should not appear after the underscore. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
Location: AnomalyDetector/stable/v1.1/openapi.json#L159
OperationIdNounVerb Per the Noun_Verb convention for Operation Ids, the noun 'Multivariate' should not appear after the underscore. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
Location: AnomalyDetector/stable/v1.1/openapi.json#L213
OperationIdNounVerb Per the Noun_Verb convention for Operation Ids, the noun 'Multivariate' should not appear after the underscore. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
Location: AnomalyDetector/stable/v1.1/openapi.json#L249
OperationIdNounVerb Per the Noun_Verb convention for Operation Ids, the noun 'Multivariate' should not appear after the underscore. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
Location: AnomalyDetector/stable/v1.1/openapi.json#L290
OperationIdNounVerb Per the Noun_Verb convention for Operation Ids, the noun 'Multivariate' should not appear after the underscore. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
Location: AnomalyDetector/stable/v1.1/openapi.json#L350
OperationIdNounVerb Per the Noun_Verb convention for Operation Ids, the noun 'Univariate' should not appear after the underscore. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
Location: AnomalyDetector/stable/v1.1/openapi.json#L400
OperationIdNounVerb Per the Noun_Verb convention for Operation Ids, the noun 'Univariate' should not appear after the underscore. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
Location: AnomalyDetector/stable/v1.1/openapi.json#L443
OperationIdNounVerb Per the Noun_Verb convention for Operation Ids, the noun 'Univariate' should not appear after the underscore. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
Location: AnomalyDetector/stable/v1.1/openapi.json#L486
⚠️ VersionConvention API version should be a date in YYYY-MM-DD format, optionally suffixed with '-preview'.
Location: AnomalyDetector/stable/v1.1/openapi.json#L5
⚠️ SecurityDefinitionDescription Security definition should have a description.
Location: AnomalyDetector/stable/v1.1/openapi.json#L60
⚠️ PageableOperation Based on the response model schema, operation 'Multivariate_GetMultivariateBatchDetectionResult' might be pageable. Consider adding the x-ms-pageable extension.
Location: AnomalyDetector/stable/v1.1/openapi.json#L69
⚠️ PaginationResponse Operation might be pageable. Consider adding the x-ms-pageable extension.
Location: AnomalyDetector/stable/v1.1/openapi.json#L69
⚠️ VersionPolicy Operation does not define an 'api-version' query parameter.
Location: AnomalyDetector/stable/v1.1/openapi.json#L73
⚠️ PathParameterSchema Path parameter should specify a maximum length (maxLength) and characters allowed (pattern).
Location: AnomalyDetector/stable/v1.1/openapi.json#L74
⚠️ ErrorResponse Error response schema should contain an object property named error.
Location: AnomalyDetector/stable/v1.1/openapi.json#L98
⚠️ VersionPolicy Operation does not define an 'api-version' query parameter.
Location: AnomalyDetector/stable/v1.1/openapi.json#L115
⚠️ Post201Response Using post for a create operation is discouraged.
Location: AnomalyDetector/stable/v1.1/openapi.json#L127
⚠️ ErrorResponse Error response schema should contain an object property named error.
Location: AnomalyDetector/stable/v1.1/openapi.json#L147
⚠️ VersionPolicy Operation does not define an 'api-version' query parameter.
Location: AnomalyDetector/stable/v1.1/openapi.json#L162
⚠️ PaginationResponse Response body schema of pageable response should contain top-level array property value
Location: AnomalyDetector/stable/v1.1/openapi.json#L184
⚠️ ErrorResponse Error response schema should contain an object property named error.
Location: AnomalyDetector/stable/v1.1/openapi.json#L196
⚠️ VersionPolicy Operation does not define an 'api-version' query parameter.
Location: AnomalyDetector/stable/v1.1/openapi.json#L216
⚠️ PathParameterSchema Path parameter should specify a maximum length (maxLength) and characters allowed (pattern).
Location: AnomalyDetector/stable/v1.1/openapi.json#L217
⚠️ ErrorResponse Error response schema should contain an object property named error.
Location: AnomalyDetector/stable/v1.1/openapi.json#L237
⚠️ VersionPolicy Operation does not define an 'api-version' query parameter.
Location: AnomalyDetector/stable/v1.1/openapi.json#L252
⚠️ PathParameterSchema Path parameter should specify a maximum length (maxLength) and characters allowed (pattern).
Location: AnomalyDetector/stable/v1.1/openapi.json#L253
⚠️ ErrorResponse Error response schema should contain an object property named error.
Location: AnomalyDetector/stable/v1.1/openapi.json#L276
⚠️ LroExtension Operations with a 202 response should specify x-ms-long-running-operation: true.
Location: AnomalyDetector/stable/v1.1/openapi.json#L289
️️✔️PR Summary succeeded [Detail] [Expand]
️️✔️[Staging] Lint(RPaaS) succeeded [Detail] [Expand]
Validation passes for Lint(RPaaS).
️️✔️Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️❌ModelValidation: 38 Errors, 0 Warnings failed [Detail]

Only 30 items are listed, please refer to log for more details.

Rule Message
REQUIRED_PARAMETER_EXAMPLE_NOT_FOUND In operation Multivariate_TrainMultivariateModel, parameter modelInfo is required in the swagger spec but is not present in the provided example parameter values.
Url: AnomalyDetector/stable/v1.1/openapi.json#L111:15
ExampleUrl: stable/v1.1/examples/TrainModel.json#L116:11
OBJECT_MISSING_REQUIRED_PROPERTY Missing required property: dataSource
Url: AnomalyDetector/stable/v1.1/openapi.json#L779:31
ExampleUrl: stable/v1.1/examples/TrainModel.json
OBJECT_MISSING_REQUIRED_PROPERTY Missing required property: startTime
Url: AnomalyDetector/stable/v1.1/openapi.json#L779:31
ExampleUrl: stable/v1.1/examples/TrainModel.json
OBJECT_MISSING_REQUIRED_PROPERTY Missing required property: endTime
Url: AnomalyDetector/stable/v1.1/openapi.json#L779:31
ExampleUrl: stable/v1.1/examples/TrainModel.json
REQUIRED_PARAMETER_EXAMPLE_NOT_FOUND In operation Multivariate_DetectMultivariateBatchAnomaly, parameter options is required in the swagger spec but is not present in the provided example parameter values.
Url: AnomalyDetector/stable/v1.1/openapi.json#L289:15
ExampleUrl: stable/v1.1/examples/DetectAnomaly.json#L301:11
OBJECT_MISSING_REQUIRED_PROPERTY Missing required property: dataSource
Url: AnomalyDetector/stable/v1.1/openapi.json#L947:55
ExampleUrl: stable/v1.1/examples/DetectAnomaly.json
OBJECT_MISSING_REQUIRED_PROPERTY Missing required property: topContributorCount
Url: AnomalyDetector/stable/v1.1/openapi.json#L947:55
ExampleUrl: stable/v1.1/examples/DetectAnomaly.json
OBJECT_MISSING_REQUIRED_PROPERTY Missing required property: startTime
Url: AnomalyDetector/stable/v1.1/openapi.json#L947:55
ExampleUrl: stable/v1.1/examples/DetectAnomaly.json
OBJECT_MISSING_REQUIRED_PROPERTY Missing required property: endTime
Url: AnomalyDetector/stable/v1.1/openapi.json#L947:55
ExampleUrl: stable/v1.1/examples/DetectAnomaly.json
REQUIRED_PARAMETER_EXAMPLE_NOT_FOUND In operation Multivariate_DetectMultivariateLastAnomaly, parameter options is required in the swagger spec but is not present in the provided example parameter values.
Url: AnomalyDetector/stable/v1.1/openapi.json#L349:15
ExampleUrl: stable/v1.1/examples/LastDetectAnomaly.json#L361:11
OBJECT_MISSING_REQUIRED_PROPERTY Missing required property: variables
Url: AnomalyDetector/stable/v1.1/openapi.json#L1074:54
ExampleUrl: stable/v1.1/examples/LastDetectAnomaly.json
OBJECT_MISSING_REQUIRED_PROPERTY Missing required property: topContributorCount
Url: AnomalyDetector/stable/v1.1/openapi.json#L1074:54
ExampleUrl: stable/v1.1/examples/LastDetectAnomaly.json
REQUIRED_PARAMETER_EXAMPLE_NOT_FOUND In operation Univariate_DetectUnivariateChangePoint, parameter options is required in the swagger spec but is not present in the provided example parameter values.
Url: AnomalyDetector/stable/v1.1/openapi.json#L399:15
ExampleUrl: stable/v1.1/examples/ChangePointDetect.json#L404:11
OBJECT_MISSING_REQUIRED_PROPERTY Missing required property: series
Url: AnomalyDetector/stable/v1.1/openapi.json#L1354:57
ExampleUrl: stable/v1.1/examples/ChangePointDetect.json
OBJECT_MISSING_REQUIRED_PROPERTY Missing required property: granularity
Url: AnomalyDetector/stable/v1.1/openapi.json#L1354:57
ExampleUrl: stable/v1.1/examples/ChangePointDetect.json
REQUIRED_PARAMETER_EXAMPLE_NOT_FOUND In operation Univariate_DetectUnivariateEntireSeries, parameter options is required in the swagger spec but is not present in the provided example parameter values.
Url: AnomalyDetector/stable/v1.1/openapi.json#L442:15
ExampleUrl: stable/v1.1/examples/EntireDetect.json#L447:11
OBJECT_MISSING_REQUIRED_PROPERTY Missing required property: series
Url: AnomalyDetector/stable/v1.1/openapi.json#L1426:46
ExampleUrl: stable/v1.1/examples/EntireDetect.json
REQUIRED_PARAMETER_EXAMPLE_NOT_FOUND In operation Univariate_DetectUnivariateLastPoint, parameter options is required in the swagger spec but is not present in the provided example parameter values.
Url: AnomalyDetector/stable/v1.1/openapi.json#L485:15
ExampleUrl: stable/v1.1/examples/LastDetect.json#L490:11
OBJECT_MISSING_REQUIRED_PROPERTY Missing required property: series
Url: AnomalyDetector/stable/v1.1/openapi.json#L1426:46
ExampleUrl: stable/v1.1/examples/LastDetect.json
REQUIRED_PARAMETER_EXAMPLE_NOT_FOUND In operation Multivariate_TrainMultivariateModel, parameter modelInfo is required in the swagger spec but is not present in the provided example parameter values.
Url: AnomalyDetector/stable/v1.1/openapi.json#L111:15
ExampleUrl: stable/v1.1/examples/TrainModel.json#L116:11
OBJECT_MISSING_REQUIRED_PROPERTY Missing required property: dataSource
Url: AnomalyDetector/stable/v1.1/openapi.json#L779:31
ExampleUrl: stable/v1.1/examples/TrainModel.json
OBJECT_MISSING_REQUIRED_PROPERTY Missing required property: startTime
Url: AnomalyDetector/stable/v1.1/openapi.json#L779:31
ExampleUrl: stable/v1.1/examples/TrainModel.json
OBJECT_MISSING_REQUIRED_PROPERTY Missing required property: endTime
Url: AnomalyDetector/stable/v1.1/openapi.json#L779:31
ExampleUrl: stable/v1.1/examples/TrainModel.json
REQUIRED_PARAMETER_EXAMPLE_NOT_FOUND In operation Multivariate_DetectMultivariateBatchAnomaly, parameter options is required in the swagger spec but is not present in the provided example parameter values.
Url: AnomalyDetector/stable/v1.1/openapi.json#L289:15
ExampleUrl: stable/v1.1/examples/DetectAnomaly.json#L301:11
OBJECT_MISSING_REQUIRED_PROPERTY Missing required property: dataSource
Url: AnomalyDetector/stable/v1.1/openapi.json#L947:55
ExampleUrl: stable/v1.1/examples/DetectAnomaly.json
OBJECT_MISSING_REQUIRED_PROPERTY Missing required property: topContributorCount
Url: AnomalyDetector/stable/v1.1/openapi.json#L947:55
ExampleUrl: stable/v1.1/examples/DetectAnomaly.json
OBJECT_MISSING_REQUIRED_PROPERTY Missing required property: startTime
Url: AnomalyDetector/stable/v1.1/openapi.json#L947:55
ExampleUrl: stable/v1.1/examples/DetectAnomaly.json
OBJECT_MISSING_REQUIRED_PROPERTY Missing required property: endTime
Url: AnomalyDetector/stable/v1.1/openapi.json#L947:55
ExampleUrl: stable/v1.1/examples/DetectAnomaly.json
REQUIRED_PARAMETER_EXAMPLE_NOT_FOUND In operation Multivariate_DetectMultivariateLastAnomaly, parameter options is required in the swagger spec but is not present in the provided example parameter values.
Url: AnomalyDetector/stable/v1.1/openapi.json#L349:15
ExampleUrl: stable/v1.1/examples/LastDetectAnomaly.json#L361:11
OBJECT_MISSING_REQUIRED_PROPERTY Missing required property: variables
Url: AnomalyDetector/stable/v1.1/openapi.json#L1074:54
ExampleUrl: stable/v1.1/examples/LastDetectAnomaly.json
️️✔️SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️ApiReadinessCheck succeeded [Detail] [Expand]
️️✔️~[Staging] SwaggerAPIView succeeded [Detail] [Expand]
️❌~[Staging] CadlAPIView: 0 Errors, 1 Warnings failed [Detail]
Rule Message
⚠️ Failed to generate cadl APIView. Please check the detail log and make sure cadl compiler version is the latest. "How to fix":"Check the detailed log and update cadl version to latest."
️️✔️CredScan succeeded [Detail] [Expand]
There is no credential detected.
️️✔️PoliCheck succeeded [Detail] [Expand]
Validation passed for PoliCheck.
️️✔️[Staging] PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️[Staging] SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️⚠️[Staging] SDK Track2 Validation: 1 Warnings warning [Detail]
  • The following tags are being changed in this PR
    • "https://github.com/openapi-env-test/azure-rest-api-specs/blob/55518ad9b4ef89697acaf143d5234cc8431b9a72/specification/cognitiveservices/data-plane/AnomalyDetector/readme.md#tag-release_1_1">cognitiveservices/data-plane/AnomalyDetector/readme.md#release_1_1
The following errors/warnings are introduced by current PR:
Rule Message
⚠️ UnkownSecurityScheme "readme":"cognitiveservices/data-plane/AnomalyDetector/readme.md",
"tag":"release_1_1",
"details":"Security scheme ApiKeyAuth is unknown and will not be processed. Only supported types are AADToken,
AzureKey,
Anonymous"
️❌CadlValidation: 2 Errors, 10 Warnings failed [Detail]
Rule Message
@azure-tools/cadl-azure-core/key-visibility-required The key property 'resultId' does not have an explicit visibility setting, please use the @visibility decorator to set it.
Location: cognitiveservices/AnomalyDetector/multivariate/models.cadl#L50
@azure-tools/cadl-azure-core/key-visibility-required The key property 'modelId' does not have an explicit visibility setting, please use the @visibility decorator to set it.
Location: cognitiveservices/AnomalyDetector/multivariate/models.cadl#L314
⚠️ @azure-tools/cadl-azure-core/use-standard-operations Operation 'DetectUnivariateEntireSeries' should be defined using a signature from the Azure.Core namespace.
Location: cognitiveservices/AnomalyDetector/univariate/routes.cadl#L10
⚠️ @azure-tools/cadl-azure-core/use-standard-operations Operation 'DetectUnivariateLastPoint' should be defined using a signature from the Azure.Core namespace.
Location: cognitiveservices/AnomalyDetector/univariate/routes.cadl#L26
⚠️ @azure-tools/cadl-azure-core/use-standard-operations Operation 'DetectUnivariateChangePoint' should be defined using a signature from the Azure.Core namespace.
Location: cognitiveservices/AnomalyDetector/univariate/routes.cadl#L40
⚠️ @azure-tools/cadl-azure-core/use-standard-operations Operation 'GetMultivariateBatchDetectionResult' should be defined using a signature from the Azure.Core namespace.
Location: cognitiveservices/AnomalyDetector/multivariate/routes.cadl#L10
⚠️ @azure-tools/cadl-azure-core/use-standard-operations Operation 'TrainMultivariateModel' should be defined using a signature from the Azure.Core namespace.
Location: cognitiveservices/AnomalyDetector/multivariate/routes.cadl#L25
⚠️ @azure-tools/cadl-azure-core/use-standard-operations Operation 'ListMultivariateModels' should be defined using a signature from the Azure.Core namespace.
Location: cognitiveservices/AnomalyDetector/multivariate/routes.cadl#L52
⚠️ @azure-tools/cadl-azure-core/use-standard-operations Operation 'DeleteMultivariateModel' should be defined using a signature from the Azure.Core namespace.
Location: cognitiveservices/AnomalyDetector/multivariate/routes.cadl#L67
⚠️ @azure-tools/cadl-azure-core/use-standard-operations Operation 'GetMultivariateModel' should be defined using a signature from the Azure.Core namespace.
Location: cognitiveservices/AnomalyDetector/multivariate/routes.cadl#L82
⚠️ @azure-tools/cadl-azure-core/use-standard-operations Operation 'DetectMultivariateBatchAnomaly' should be defined using a signature from the Azure.Core namespace.
Location: cognitiveservices/AnomalyDetector/multivariate/routes.cadl#L96
⚠️ @azure-tools/cadl-azure-core/use-standard-operations Operation 'DetectMultivariateLastAnomaly' should be defined using a signature from the Azure.Core namespace.
Location: cognitiveservices/AnomalyDetector/multivariate/routes.cadl#L131
Posted by Swagger Pipeline | How to fix these errors?

@openapi-pipeline-app-test
Copy link

openapi-pipeline-app-test bot commented Jan 9, 2023

Swagger Generation Artifacts

️️✔️[Staging] ApiDocPreview succeeded [Detail] [Expand]
 Please click here to preview with your @microsoft account. 
️️✔️[Staging] SDK Breaking Change Tracking succeeded [Detail] [Expand]

Breaking Changes Tracking

️️✔️ azure-sdk-for-net-track2 succeeded [Detail] [Expand]
  • ️✔️Succeeded [Logs] Generate from 74616c1d15b40a51ad2343efcb3ece2c3ad6b306. 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
  • ️✔️Azure.AI.AnomalyDetector [View full logs]  [Preview SDK Changes]
    info	[Changelog]
️⚠️ azure-sdk-for-python warning [Detail]
  • ⚠️Warning [Logs] Generate from 74616c1d15b40a51ad2343efcb3ece2c3ad6b306. 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] WARNING: Skipping azure-nspkg as it is not installed.
    warn		specification/cognitiveservices/data-plane/AnomalyDetector/readme.md skipped due to azure-sdk-for-python not found in swagger-to-sdk
    command	sh scripts/automation_generate.sh ../azure-sdk-for-python_tmp/generateInput.json ../azure-sdk-for-python_tmp/generateOutput.json
    cmderr	[automation_generate.sh]  notice
    cmderr	[automation_generate.sh] npm notice New minor version of npm available! 9.3.1 -> 9.5.1
    cmderr	[automation_generate.sh] npm notice Changelog: <https://github.com/npm/cli/releases/tag/v9.5.1>
    cmderr	[automation_generate.sh] npm notice Run `npm install -g [email protected]` to update!
    cmderr	[automation_generate.sh] npm notice
    warn	No file changes detected after generation
    warn	No package detected after generation
️️✔️ azure-sdk-for-js succeeded [Detail] [Expand]
  • ️✔️Succeeded [Logs] Generate from 74616c1d15b40a51ad2343efcb3ece2c3ad6b306. 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
    warn		specification/cognitiveservices/data-plane/AnomalyDetector/readme.md skipped due to azure-sdk-for-js not found in swagger-to-sdk
    command	sh .scripts/automation_generate.sh ../azure-sdk-for-js_tmp/generateInput.json ../azure-sdk-for-js_tmp/generateOutput.json
    cmderr	[automation_generate.sh] [ERROR] Generate changelog failed: ENOENT: no such file or directory, open '/mnt/vss/_work/1/s/azure-sdk-for-js/sdk/anomalydetector/ai-anomaly-detector-rest/changelog-temp/package/CHANGELOG.md'
  • ️✔️@azure-rest/ai-anomaly-detector [View full logs]  [Preview SDK Changes]
    info	[Changelog]
    error	breakingChangeTracking is enabled, but version or changelogItem is not found in output.
️⚠️ azure-sdk-for-java warning [Detail]
  • ⚠️Warning [Logs] Generate from 74616c1d15b40a51ad2343efcb3ece2c3ad6b306. 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
    cmderr	[init.sh] [notice] A new release of pip is available: 23.0 -> 23.0.1
    cmderr	[init.sh] [notice] To update, run: pip install --upgrade pip
    cmderr	[init.sh] [notice] A new release of pip is available: 23.0 -> 23.0.1
    cmderr	[init.sh] [notice] To update, run: pip install --upgrade pip
    warn		specification/cognitiveservices/data-plane/AnomalyDetector/readme.md skipped due to azure-sdk-for-java not found in swagger-to-sdk
    command	./eng/mgmt/automation/generate.py ../azure-sdk-for-java_tmp/generateInput.json ../azure-sdk-for-java_tmp/generateOutput.json
    cmderr	[generate.py] npm notice
    cmderr	[generate.py] npm notice New major version of npm available! 8.19.3 -> 9.5.1
    cmderr	[generate.py] npm notice Changelog: <https://github.com/npm/cli/releases/tag/v9.5.1>
    cmderr	[generate.py] npm notice Run `npm install -g [email protected]` to update!
    cmderr	[generate.py] npm notice
  • ️✔️azure-ai-anomalydetector [View full logs]  [Preview SDK Changes]
Posted by Swagger Pipeline | How to fix these errors?

@openapi-pipeline-app-test
Copy link

openapi-pipeline-app-test bot commented Jan 9, 2023

@ruowan
Copy link
Author

ruowan commented Jan 9, 2023

/azp run

@azure-pipelines
Copy link

No pipelines are associated with this pull request.

@ruowan
Copy link
Author

ruowan commented Jan 9, 2023

/azp run

@azure-pipelines
Copy link

No pipelines are associated with this pull request.

@ruowan
Copy link
Author

ruowan commented Jan 9, 2023

/azp run

@azure-pipelines
Copy link

No pipelines are associated with this pull request.

@ruowan
Copy link
Author

ruowan commented Jan 9, 2023

/azp run

@azure-pipelines
Copy link

No pipelines are associated with this pull request.

@ruowan
Copy link
Author

ruowan commented Jan 9, 2023

/azp run

@azure-pipelines
Copy link

No pipelines are associated with this pull request.

@ruowan
Copy link
Author

ruowan commented Jan 9, 2023

/azp run

@azure-pipelines
Copy link

No pipelines are associated with this pull request.

@ruowan
Copy link
Author

ruowan commented Jan 10, 2023

/azp run

@azure-pipelines
Copy link

No pipelines are associated with this pull request.

@ruowan
Copy link
Author

ruowan commented Feb 27, 2023

/azp run

@azure-pipelines
Copy link

No pipelines are associated with this pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants