-
Notifications
You must be signed in to change notification settings - Fork 316
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
Default :per_page parameter is ignored #137
Comments
Hi Serge, do you have time to look into this and submit PR? |
I will look into this |
We just upgraded from v0.11.3 to v0.12.2 of the gem and were bit by a problem that looks very much like this: when our GitHub connection is initialized with a "default" :per_page setting of 100, branches are missing when they are listed from a repository (i.e. they just don't show up in the resultset). Without setting a "default" :per_page (i.e. if we just don't configure that part), everything is listed correctly. The difference is that simple: Causes some branches to be missing from the result:
Works properly (no branches missing):
|
Thanks for letting me know, this is indeed strange behaviour. Does |
github_cli sanity check
Without setting .per_page on the connection
With setting .per_page on the connection
This problem appears trivially/easily reproducible -- I've never attempted to reproduce it and failed. |
When API instance is created with default :per_page parameter
First request is always sent without parameters and autopagination uses default 30 page size.
The text was updated successfully, but these errors were encountered: