-
Notifications
You must be signed in to change notification settings - Fork 66
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
Bot account hitting rate limit (again?) #5032
Comments
I'm pretty sure this is suo's token in the github-status-test lambda PATs have rate limit of 5000/user/hr They get refreshed every hour, so this problem will resolve itself and then maybe show up in an hour. A look on rockset says that we are occasionally hitting 4900+ workflow jobs on pytorch during peak working hours (this doesn't include all the other repos but idk which ones are sending webhooks here), but this averages to ~1600/hr over the entire week Here are some possible solutions:
|
I guess we need to stop using Suo's token anyway, that's not a good practice to keep. So we can do the It seems easier to use the second approach using our other bot accounts that have PAT. Don't need to go through the pytorchbot app route which will requires OIDC connection from Vercel to our AWS account, which is not supported atm #4789 (comment) |
Here are some docs on how to authenticate as a Github App: https://docs.github.com/en/apps/creating-github-apps/authenticating-with-a-github-app/authenticating-as-a-github-app |
Added ability to use more tokens in #5033
|
We are seeing more
{"message":"API rate limit exceeded for user ID 1617424. If you reach out to GitHub Support for help, please include the request ID 9E6E:0A32:178BB2:2A26F7:65FB3545.","documentation_url":"https://docs.github.com/rest/overview/rate-limits-for-the-rest-api"}
error from CI logs, i.e. https://ossci-raw-job-status.s3.amazonaws.com/log/22898061143. This is a new issue and we need to take a closer look to find out the root cause and potential fixes.cc @clee2000 @PaliC @kit1980 @malfet
The text was updated successfully, but these errors were encountered: