-
Notifications
You must be signed in to change notification settings - Fork 5.3k
Add the missing description to summarization parameter #20809
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
Conversation
Swagger Validation Report
|
Rule | Message |
---|---|
Runtime Exception |
"new":"https://github.com/Azure/azure-rest-api-specs/blob/f5c0456ac16dbf7c3c1ce3e9f4b332a36e8bd1a5/dev/cognitiveservices/data-plane/Language", "old":"https://github.com/Azure/azure-rest-api-specs/blob/main//mnt/vss/_work/1/same-version-c93b354fd9c14905bb574a8834c4d69b/dev/cognitiveservices/data-plane/Language", "details":"Command failed: node /mnt/vss/_work/_tasks/AzureApiValidation_5654d05d-82c1-48da-ad8f-161b817f6d41/0.0.42/common/temp/node_modules/.pnpm/@Azure[email protected]/node_modules/autorest/dist/app.js /tmp/readme.oad.old.md --v2 --tag=oad-default-tag --output-artifact=swagger-document.json --output-artifact=swagger-document.map --output-file=old --output-folder=/tmp\nFATAL: swagger-document/compose - FAILED\nFATAL: Error: '$["x-ms-parameterized-host"].hostTemplate' has incompatible values (---\n'Endpoint/language'\n, ---\n'Endpoint/language/authoring'\n).\n Error: '$["x-ms-parameterized-host"].hostTemplate' has incompatible values (---\n'Endpoint/language'\n, ---\n'Endpoint/language/authoring'\n).\n" |
BreakingChangeToolException |
"details":""errno":-21, "syscall":"read", "code":"EISDIR"" |
️️✔️
Breaking Change(Cross-Version) succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️
CredScan succeeded [Detail] [Expand]
There is no credential detected.
️❌
LintDiff: 2 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 |
"location":"dev/cognitiveservices/data-plane/Language/readme.md", "tag":"release_2022-07-01-preview", "details":"swagger-document/compose - FAILED" |
|
AutoRest exception |
"location":"dev/cognitiveservices/data-plane/Language/readme.md", "tag":"release_2022-07-01-preview", "details":"Error: '$["x-ms-parameterized-host"].hostTemplate' has incompatible values (---'Endpoint/language', ---'Endpoint/language/authoring')." |
The following errors/warnings exist before current PR submission:
Rule | Message |
---|---|
A LRO Post operation with return schema must have 'x-ms-long-running-operation-options' extension enabled. Location: cognitiveservices/data-plane/Language/questionanswering-authoring.json#L263 |
️️✔️
Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️
ApiReadinessCheck succeeded [Detail] [Expand]
️️✔️
~[Staging] ServiceAPIReadinessTest succeeded [Detail] [Expand]
Validation passes for ServiceAPIReadinessTest.
️️✔️
~[Staging] TrafficValidation 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.
️️✔️
SDK Track2 Validation succeeded [Detail] [Expand]
Validation passes for SDKTrack2Validation
️️✔️
PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️
SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️
Lint(RPaaS) succeeded [Detail] [Expand]
Validation passes for Lint(RPaaS).
️️✔️
CadlValidation succeeded [Detail] [Expand]
Validation passes for CadlValidation.
️️✔️
PR Summary succeeded [Detail] [Expand]
Validation passes for Summary.
Hi, @wangyuantao Thanks for your PR. I am workflow bot for review process. Here are some small tips. Any feedback about review process or workflow bot, pls contact swagger and tools team. [email protected] |
Swagger Generation Artifacts
|
Swagger pipeline restarted successfully. If there is ApiView generated, it will be updated in this comment. |
Hi @wangyuantao, Your PR has some issues. Please fix the CI sequentially by following the order of
|
I'm also very confused what we should do from here. |
@lmazuel can you merge this? The error is still saying |
@@ -32,7 +32,7 @@ | |||
} | |||
], | |||
"x-ms-parameterized-host": { | |||
"hostTemplate": "{Endpoint}/language/authoring", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we know the reason for this change ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It causes validation error. Let me revert this, and request exception.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Standalone fix for this: #20927
"description": "Supported Cognitive Services endpoint (e.g., https://<resource-name>.api.cognitiveservices.azure.com).", | ||
"x-ms-parameter-location": "client", | ||
"required": true, | ||
"type": "string", | ||
"format": "uri", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is to make consistent with July preview. Is that OK? @heaths
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For anything new, I recommend declaring the uri
format. The others should've been before, but it's consider a breaking change to do it after. Most languages will ignore it anyway and just do a string, but some lanugages - like C# - actually end up using a Uri
class (correctly). If you don't, we'll have to transform it and we're trying to avoid that. The swaggers should be the main source of truth. They are the spec, afterall. :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@heaths there are so many conflict rules and I'm confused which rule trump which rule... This is existing stuff, not new. In /specification folder, the latest stable version and the latest preview has no format, only /dev folder has format uri. Given we cannot break anything GA, we should fix /dev folder as what I'm doing here - remove format uri, right?
@@ -285,12 +285,6 @@ | |||
"application/json" | |||
], | |||
"responses": { | |||
"200": { | |||
"description": "Export job status, project metadata, and assets.", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
200 response is needed for SDK. Heath have added this in our earlier swaggers. There will be a validation error but that can be overriden.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in example.
@@ -1540,12 +1538,11 @@ | |||
}, | |||
"parameters": { | |||
"Endpoint": { | |||
"name": "Endpoint", | |||
"name": "endpoint", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In /specification folder, the latest stable is uppercase "Endpoint", and latest preview is lowercase "endpoint", so no matter what we do here, it is a breaking change. So I will revert this to keep it in uppercase "Endpoint" so no breaking change to GA version. @heaths, Is that OK?
@@ -13,6 +13,18 @@ | |||
} | |||
}, | |||
"responses": { | |||
"200": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Data Plane API - Pull Request
API Info: The Basics
Most of the information about your service should be captured in the issue that serves as your engagement record.
Is this review for (select one):
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 Open API document (swagger) if applicable, and the root paths that have been updated.
❔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