-
Notifications
You must be signed in to change notification settings - Fork 28
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
API Rate Limit exceeded errors #96
Comments
Thanks for using it! And thanks for reporting this issue. I'll check tomorrow. Most likely some of the API calls don't use the provided github-token. Should be easy to fix. One question - did you provide the token yourself? GitHub is printing action arguments with default values |
It should be fixed now. Please update to 12.2. Hopefully, you will not see rate limit error ever again :) |
Thank you! |
Hey there, thanks a lot for your work! |
Hi @DeLaGuardo! I hit a rate limit today, could be legit or maybe... Did the |
On several projects using setup-clojure I've been encountering occasional failures from API rate limits.
As example:
Unfortunately, it's not clear from the error what documentation needs to be checked in order to authenticate for a higher rate limit.
It looks like this was previously encountered in #40 but was then removed in #45. From the error message I can't be sure, but I wonder if the fetch step for CLI is passing the token correctly but the corresponding logic for fetching babashka is not using a token?
I'm also using caching, but I'm curious if using latest instead of a specific version might be forcing cache misses.
Thank you very much for this very useful github action, hopefully we can find a solution to address the sporadic failures.
The text was updated successfully, but these errors were encountered: