Skip to content
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

Recognise and handle GitHub's rate-limiting #201

Open
str4d opened this issue May 17, 2016 · 0 comments
Open

Recognise and handle GitHub's rate-limiting #201

str4d opened this issue May 17, 2016 · 0 comments

Comments

@str4d
Copy link
Contributor

str4d commented May 17, 2016

While investigating another bug I ran into GitHub's rate-limiting (which itself triggered the bug fixed in #200). github.py currently uses caching in some cases, but ignores the returned header values as well as the HTTP error code when the limit is reached. It should be aware of the current limits and degrade gracefully when it is not possible to load all necessary commits.

@str4d str4d changed the title Recognise and stay within GitHub's rate-limiting Recognise and handle GitHub's rate-limiting May 17, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant