You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
str4d
changed the title
Recognise and stay within GitHub's rate-limiting
Recognise and handle GitHub's rate-limiting
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.The text was updated successfully, but these errors were encountered: