Closed dgtized closed 9 months ago
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
I did not try providing a token, as it wasn't in the documentation. When I dug through and found #40 I considered it but wasn't sure if #45 actually removed the need for that?
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! Just wanted to give you a heads-up that I just saw an occurrence of this with version 12.3 at https://github.com/imrekoszo/polylith-kaocha/actions/runs/7709816905/job/21011785765
Hi @DeLaGuardo! I hit a rate limit today, could be legit or maybe...
Did the setup
for cli
maybe not get updated to use githubAuth
?
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.