-
Notifications
You must be signed in to change notification settings - Fork 145
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
Next Page in Iteration fails #114
Comments
This looks like a DNS resolution error. Can you |
Not likely as the first set come through just fine. This is failing on getting the next page. I ran the same query with curl, then got page 2, and it worked fine. |
I haven't looked into this yet @rsalesas, is it still an issue for you? I'm going to do some work around getting v3 released soon, so I should get to this while doing that. |
+1 on this; I have hit this same exact issue as well with the 3.0b2 branch (this issue is NOT PRESENT in version 2.1.1) I had to write a hacky manual pagination loop (sending page='2', etc, after a for loop of 20 elements) in the meantime, but any chance this issue will get some attention soon? Same goes for conversations and leads; it only prints the first page for each (as such):
|
I just merged #125 which is related to next_link in collection_proxy. I think this may have resolved this issue. |
How come you can't see the failure when you test?
|
I wasn't able to reproduce it last time I looked at it (don't know if that was a fault with the test or not). I haven't tested it this time around, I'm just letting you know that the PR might have resolved it as it was to do with pagination. The issue is still open. |
OK I’ll give it another shot. Stopped using it, as it didn’t work.
|
Sorry about that @rsalesas. I see a window of time opening up a bit for me so we'll get the version 3 release out the door soonish anyway. This should be fixed in that release. |
@rsalesas This is fixed in 3.0. |
Hi, I'm running the following code and it fails consistently both in users and leads when it needs to page.
This happens in Python 2.7 or 3.0
for lead in intercom.leads.all(): print(lead.email)
for user in intercom.users.all(): print(user.email)
Error is:
The text was updated successfully, but these errors were encountered: