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
Paginators #391
Comments
ah nice catch! Looks like we need to consider empty tokens and not just unset tokens. cc @kggilmer services can reply with the nextToken field present but empty apparently. |
I have a fix for this, we will release a patch ASAP. |
@tschuett as an aside, you can simplify that code a little bit by using the non-setter versions that accept explicit values instead of options/vecs: let paginator = client
.describe_spot_price_history()
.instance_types(instance_type)
.product_descriptions("Linux/UNIX")
.availability_zone("eu-north-1a")
.into_paginator()
.items()
.send(); |
fixed in 0.4.1 |
|
What is the problem?
The following does not terminate:
pre paginators, I used:
Version
Platform
OSX
AWS Services
ec2
Description
No response
Logs
The next token looks odd.
The text was updated successfully, but these errors were encountered: