When I try to get all members of a project which has more than per_page members, some of members are repeated on different pages of json. For example, if I set per_page=1, I get the same user at second and third pages.
Platform (Android, iOS, Website):
URLs (aka web addresses) of any relevant observations or pages:
it doesn’t seem like the results returned by the endpoint are ordered in any logical way. if they’re not consistently ordered, then maybe that explains why a given member might show up on different pages of results for no good reason?
I also encountered this bug the other day, and found a workaround:
Add &order_by=login to the end of the query.
This will order by user member login names rather than by observation count, which is the default order, and seems to solve the problem of missing users.
My guess at the reason behind the behaviour is where one page ends and another starts, if there’s users with the same number of observations, it’s possible to receive the same user at the start of one page, and the end of another, which effectively hides the user that should have been returned instead.