-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
get-log-events on 1.8.1 is giving: Error during pagination: The same next token was received twice #1485
Comments
Error also occurs in 1.8.0, does not occur in 1.7.47 |
Paginators were added in this botocore PR: boto/botocore#627 But |
May be the fault of botocore? v1.1.10 on 1.7.47 |
Yeah |
Ah: boto/botocore@661b42f. This needs to be reverted. cc @kyleknap |
Should be fixed now. Closing |
A new version hasn't been released yet, so there's no way to test this without checking out from git, right? I quite like how on https://github.com/aws/aws-sdk-js issues don't get closed until a version with the fix is released – that way issue commenters/raisers can verify that their issue is fixed. Any chance this repo and/or botocore could follow the same process? |
Awesome, just noticed 1.8.2 just got released, upgraded and all good, thanks! 👍 |
Upgraded aws-cli recently to 1.8.1 – not sure exactly what version before but it was 1.7.x
I'm now getting this:
This is breaking all of our log monitoring scripts in production right now
I'm going to try and bisect and see what version might have caused it, but if there's anything that might point me in the right direction, that would be appreciated!
The text was updated successfully, but these errors were encountered: