Skip to content
This repository was archived by the owner on Jul 22, 2024. It is now read-only.

Conversation

@msize
Copy link

@msize msize commented Feb 13, 2020

Description

Fix pagination

Related issue

Fixes #114

@msize msize requested a review from a user February 13, 2020 06:22
@msize
Copy link
Author

msize commented Feb 20, 2020

@IsaiahWilliams What you think about this behavior of PC API? When it returns 204 no content on the next link? The full result of the getUtilization operation is not consistent and should be failed.

@msize msize changed the title Fix pagination Issue #114 Fix pagination Feb 26, 2020
@ghost
Copy link

ghost commented Jun 16, 2020

@msize thank you for putting this together. With respect to this feature of the API the HTTP 204 response is expected if no data is available for the requested period of time. However, what is interesting is that you are getting the next link from the API. So, it should have data available for you. By chance do you have the correlation and request identifier for the call that is failing?

@msize
Copy link
Author

msize commented Jun 29, 2020

@IsaiahWilliams I've checked for our old issues with these cases and found one:

Request: utilizations/azure?seek_operation=Next
Response: 204 No Content
Response headers:

        Content-Length: 0
        Retry-After: Mon, 27 Jan 2020 04:17:10 GMT
        MS-CorrelationId: b2205c7c-6b5f-4e98-83f4-4866050e123c
        MS-RequestId: efdb0bd8-fd61-4ada-98ef-8493ad5fdd42
        X-Locale: en-US
        MS-CV: hZpIl3FA50WfX12p.0
        MS-ServerId: 1000000
        Request-Context: appId=cid-v1:03ce8ca8-8373-4021-8f25-d5dd45c7b12f
        Date: Mon, 27 Jan 2020 04:02:10 GMT

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant