Skip to content

fix(core): total_count legacy #595

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

Merged
merged 3 commits into from
Jul 24, 2024
Merged

Conversation

Laure-di
Copy link
Contributor

close #555
close #550

@Laure-di Laure-di requested a review from remyleone as a code owner July 11, 2024 15:23
@@ -168,6 +166,12 @@ def _request(
verify=not self.client.api_allow_insecure,
)

if response.headers.get("x-total-count"):
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we have tests for it ? We can use listServerTypes as it does not require a token.

@Laure-di Laure-di force-pushed the fix/total-count branch 2 times, most recently from a9a4dd8 to f06b3c8 Compare July 15, 2024 14:43
@xxbillouxx
Copy link

xxbillouxx commented Jul 22, 2024

Hi !
When the next release (including the fix) is planned ?
Thanks

@remyleone remyleone added this pull request to the merge queue Jul 24, 2024
Merged via the queue into scaleway:main with commit 71d55bc Jul 24, 2024
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Mishandling of total_count value in instance API make the instance API unusable list_servers_types throws exception
4 participants