-
-
Notifications
You must be signed in to change notification settings - Fork 130
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
streams over paginate loop over the same record over and over again #466
Comments
ah okay so 0.25 works, 0.26 doesnt and I think it has to do with what is noted in the changelog about changes to List |
Thanks @jessfraz - hoping this will be fixed by pagination changes in #452. If possible, it would be extremely helpful if you could capture the sequence of stripe responses to your sample code (or just debug printing the first 2 returned |
yes will get you some json from our "test mode" today! thank you! |
you know what is weird... it just started working fine on 0.26, my test that was failing is now passing, when i tried to get you the debug output |
maybe it was a server side stripe thing because I swear its the same code |
Thanks for looking into it - that's strange! Think this is good to leave open regardless because I wouldn't be surprised if it's a weird pagination edge case. |
Okay it is def a weird edge case, in that previously it was happening on listing invoice items, but now it is happening on listing invoices. here is the debug ooutput of listing invoices when it happens This is in our stripe test mode so nothing is bad or a secret.
|
I think it happens when there is only one item in the list? |
I see the same and based on the above tip, this workaround is helping
EDIT: actually not working 100% of the time |
I am hoping this issue will be nuked once the rewrite lands. If you are able to produce a unit test or even a set of json requests / responses I will try to understand what is wrong. |
Describe the bug
some sample code:
To Reproduce
see above sorry!
Expected behavior
Previous we were on version 0.21 now on 0.26 we see this bug. Without the code changing it appeared. So i would expect the stream to stop after its gotten all the records
Code snippets
No response
OS
macos
Rust version
1.75.0
Library version
0.26.0
API version
whatever the default is for the library?
Additional context
No response
The text was updated successfully, but these errors were encountered: