-
Notifications
You must be signed in to change notification settings - Fork 331
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
Deploying multiple runners fails with github rate limit after version 0.5.0
#655
Comments
Its GH limiting the api requests... It seems to be requesting lots of pages in your case. Originally we were not paginating since one page of online runners sufficed. It should be an easy fix 🙏 |
Are we really performing that many requests? Authenticated calls have generous limits. |
It seems so! Or at least its what the error says.
|
Eight pages of runners? 🙀 |
this is very interesting. const promises = [];
for (let i = 0; i < 5000; i++) {
promises.push(cml.runnerByName({ name }));
}
await Promise.all(promises) sounds to me a lot! Are you triggering that much events @thatGreekGuy96 ? We might be loosing something |
As far as I'm aware, I'm just calling 'cml-runner' 30 times, so nowhere near 5000. I don't know how many calls to GitHub's API happen within that command though. |
30 x 8 pages... that I know based on your logs |
@thatGreekGuy96, given that all the calls are being made concurrently from the different Maybe you could send them in batches. It's going to be slower, but probably not that much. for ((runner=0; runner<runners; runner++)); do ((runner%10)) || wait
cml-runner ··· &
done
wait |
I'll give that a try, it shouldn't have too big of an impact. |
Im finishing the PR adding throttling and being smarter when consuming it |
Hey everyone,
Noticed the following error appearing from version
0.5.0
onwards. We have a stage in our github actions pipeline that deploys multiple runners, as such:I noticed that the following error has started appearing after version
0.5.0
of cml was released:Any clues as to what would be going on? Reverting to
0.4.7
fixed the problem.The text was updated successfully, but these errors were encountered: