-
Notifications
You must be signed in to change notification settings - Fork 192
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
rate_limit endpoint throws if over rate limit (LOL?) #856
Comments
Does it work at all? :) |
should probably be
|
So, actually the root /rate_limit endpoint is always broken, the /api/rate_limit one is broken only when GitHub is not playing along. (The fix above will ensure both endpoints are broken only when GitHub acts up) |
We must have broken it at some point, it used to work in the past yes. |
s/We/I/ -- I think I unintentionally broke this when I refactored stuff into |
The API changed. https://developer.github.com/v3/rate_limit/ rate will be dropped at a point. But indeed the get sends back a list:
And the refactoring happened when working on #827 We were returning |
Thanks for the diagnosis, @karlcow. |
/me is looking at a fix and a test. |
Pull request done. I have another worry which is not totally related to this issue.
No matter how many search I tried to execute in 1 minute, I don't get a change on the search rate limit. Weird. |
Hm, maybe we never end up using those webcompat bot search requests. If you're logged in, it goes through webcompat as your account. If you're logged out, we bypass webcompat and make those requests via the client as unauthenticated ones. |
STR:
3):
The text was updated successfully, but these errors were encountered: