Azure / azure-rest-api-specs

The source for REST API specifications for Microsoft Azure.
MIT License
2.67k stars 5.09k forks source link

[BUG] calculateModelCapacity method returns 404 #30403

Open antonyscerri opened 2 months ago

antonyscerri commented 2 months ago

API Spec link

https://github.com/Azure/azure-rest-api-specs/blob/main/specification/cognitiveservices/resource-manager/Microsoft.CognitiveServices/preview/2024-06-01-preview/cognitiveservices.json#L1075

API Spec version

2024-06-01-preview

Describe the bug

The calculateModelCapacity method appears to return 404 no matter what parameter values you try. In the sample provided the skuName value has what looks like a typo "ProvisinedManaged" but doesnt work with or without.

Expected behavior

Providing valid parameters should not return a 404 error.

Actual behavior

Returns 404 error with any parameter combination as specified in the spec

Reproduction Steps

Use the provided example substituting a valid subscription ID returns a 404.

Environment

Tried with curl, python requests etc, not a client side issue.

v-jiaodi commented 2 months ago

@tianxin-ms Please help take a look, thanks.

tianxin-ms commented 2 months ago

We're working on this now, ETA about 3-4 weeks

antonyscerri commented 2 months ago

Should it be in the published API specification if its not there? Could the documentation at least say if its not implemented. If unimplemented methods are in the API specification then maybe they should return a more appropriate response than a generic 404, an error payload with a description stating it is not yet implemented. It will reject the request if you supply an earlier API specification version. A 404 suggests something else might be wrong rather than it not being implemented.

tianxin-ms commented 2 months ago

I understand you complain, we put this API in a preview version for the unexpected problems, and it does take more time than expected to handle some issues. I will let API owner know this and have some updates on this or the documentation.

antonyscerri commented 1 month ago

Could you provide an update on whether this might be available in the next couple of days or nor? Thanks

antonyscerri commented 3 weeks ago

Is there any update on the implementation of the missing function?

antonyscerri commented 3 weeks ago

I see there is a new API version 2024-10-01. This now seems to return a HTTP 500 error.

tianxin-ms commented 2 weeks ago

Checked with API owner, this has been fixed and getting rolled out, the ETA is the end of this week to all the regions.