Skip to content
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

Closed
mhart opened this issue Sep 2, 2015 · 8 comments

Comments

@mhart
Copy link

mhart commented Sep 2, 2015

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:

$ aws logs get-log-events --log-group-name <log-group> --log-stream-name <log-stream>
Error during pagination: The same next token was received twice: [u'f/32138893253961162432958564326845666539453351348553515008']

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!

@mhart
Copy link
Author

mhart commented Sep 2, 2015

Error also occurs in 1.8.0, does not occur in 1.7.47

@jamesls
Copy link
Member

jamesls commented Sep 2, 2015

Paginators were added in this botocore PR: boto/botocore#627

But GetLogEvents was explicitly taken out, specifically because of this. Let me track down what happened.

@mhart
Copy link
Author

mhart commented Sep 2, 2015

May be the fault of botocore? v1.1.10 on 1.7.47

@mhart
Copy link
Author

mhart commented Sep 2, 2015

Yeah

@jamesls
Copy link
Member

jamesls commented Sep 2, 2015

Ah: boto/botocore@661b42f. This needs to be reverted.

cc @kyleknap

@kyleknap
Copy link
Contributor

kyleknap commented Sep 2, 2015

Should be fixed now. Closing

@kyleknap kyleknap closed this as completed Sep 2, 2015
@mhart
Copy link
Author

mhart commented Sep 3, 2015

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?

@mhart
Copy link
Author

mhart commented Sep 3, 2015

Awesome, just noticed 1.8.2 just got released, upgraded and all good, thanks! 👍

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

No branches or pull requests

3 participants