-
Notifications
You must be signed in to change notification settings - Fork 23
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
GitHub API rate limiting #93
Milestone
Comments
Agreed, this is something we should fix. It has already been a problem: fair-software/howfairis-github-action#36 |
When recordings are used in tests we should filter the token out of the recording so they don't leak. See https://vcrpy.readthedocs.io/en/latest/advanced.html#filter-sensitive-data-from-the-request |
Merged
Issue was auto-closed by fix keyword, reopening |
jspaaks
added a commit
that referenced
this issue
Feb 20, 2021
jspaaks
added a commit
that referenced
this issue
Feb 20, 2021
…r range notaion to a less ambiguous style
PR was merged, closing |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The GitHub API is used anonymously in this library. If used more than 60 req per hour the API will say no. This limit could be reached when asserting a bunch of software like on https://www.research-software.nl/ .
One way to solve is to use an OAuth token which will up the limit to 5000 req per hour. It would be nice if the howfairis tool would allow passing a GitHub OAuth token either as environment variable or as command line argument.
GitLab also has rate limit, but is much higher so not such a problem.
The text was updated successfully, but these errors were encountered: