github-readme-stats
github-readme-stats copied to clipboard
anuraghazra
[Down Time] Card throws 'maximum retries exceeded' error
Hi everyone, I see that all personal access tokens are currently failing, thus you will see the "Maximum retries exceeded" error.
I'm looking into the issue to figure out what caused it.
Ideally, it should be fixed in an hour when the PATs get rest.
Details
Public instance information
Explanation
Hey everyone, sorry for the recent downtimes.
For the sake of transparency, we get a huge amount of requests per month (it's kind of mind boggling for a side project which I built just for fun). Here's the vercel dashboard statistics:
As you can see even with 73% of the responses being cached by vercel the amount of live requests are huge, and the bottleneck here is Personal Access Tokens
Each PAT have 5000 points, and based on the complexity of the GraphQL query & resource limitations set by GitHub, it's actually very very low considering that amount of requests.
To circumvent the issue, we currently have 7 PATs (thats 35k points) which sometimes get exhausted. Thanks to @rickstaa we are going to add few more probably bumping it up to 10 or 12, hopefully that could help alleviate the downtimes.
Note: That these downtimes are temporary, and only lasts for 1hour, since PATs regenerate after 1 hour
So whats the idea way?
https://github.com/anuraghazra/github-readme-stats/issues/1471#issuecomment-979306704 Deploy on your own vercel instance. WHY? It's easy to do, free & reliable.
- It reduces loads on our vercel instance.
- Your own PAT will give you more concrete stats including private stats
- It ensures that there won't be any downtime on your profile stats because you are the only one who is gonna hit your URL
Originally posted by @anuraghazra in https://github.com/anuraghazra/github-readme-stats/issues/2130#issuecomment-1270624232
@anuraghazra hi, the access is still down. Do we have an expected time to fix it?
Never imagined that my profile would be that much dependent on the GitHub stats , 😁. Hope that will be done soon, nice work man.
Hi everyone.
Sorry for the inconvenience. I will highly recommend deploying github-readme-stats on your own vercel instance to fix this issue, while I try to find a fix. Currently I'm unable to find any root cause.
Consider deploying on your own fork. follow the guide -> https://github.com/anuraghazra/github-readme-stats#deploy-on-your-own-vercel-instance
Youtube video tutorial: https://www.youtube.com/watch?v=n6d4KHSKqGk&feature=youtu.be&t=107
Also after forking make sure to open vercel.json and change the maxDuration option to 10.
Thanks a lot! mine is already bug fixed
Yes, it's happening intermittently for some people, and for some it's not.
He is working on the fix, till then, he said to run it on our own vercel instance
Hi everyone.
Sorry for the inconvenience. I will highly recommend deploying github-readme-stats on your own vercel instance to fix this issue, while I try to find a fix. Currently I'm unable to find any root cause.
Consider deploying on your own fork. follow the guide -> https://github.com/anuraghazra/github-readme-stats#deploy-on-your-own-vercel-instance
Youtube video tutorial: https://www.youtube.com/watch?v=n6d4KHSKqGk&feature=youtu.be&t=107
Also after forking make sure to open vercel.json and change the maxDuration option to 10.
Added 4 new PATs, let's observe the downtime. For some reason the PATs are weirdly depleting super fast. not sure why.
ALSO: Note that deploying on your own instance is ALWAYS a better option than relaying on ours
- It reduces loads on our vercel instance, we get almost 3-4Million requests per month which is hard to scale up.
- Your own PAT will give you more concrete stats including private stats
- It ensures that there won't be any downtime on your profile stats because you are the only one who is gonna hit your URL
So please I enocurage everyone to deploy on their own instance, If you face any kind of issues while deployment I'm more than happy to help you out.
Yes, it's happening intermittently for some people, and for some it's not.
Right, it is failing intermittently - checked around 6 PM IST. As @anuraghazra suggested already: deploying github-readme-stats on your own vercel instance would be a better option as of now.
Yaah same problem here, now going forward I 'am planning to deploy this in personal vercel app :)
Hi folks, I think the PATs are again depleting (even though we have 6 PATs now)
Please consider https://github.com/anuraghazra/github-readme-stats/issues/1471#issuecomment-979306704
It works well on this hour, and I have deploy on my own vercel, to take a little less stress on this repository's vercel instance :)
@anuraghazra Maybe we should add this to the bug template FAQ (i.e. https://github.com/anuraghazra/github-readme-stats/edit/master/.github/ISSUE_TEMPLATE/bug_report.md)? Also, maybe it is better to put the FAQ on top?
It looks like 9d2bfd9d8f00f6fc5229d0174a220ba04dbc4ee8 fixed this issue for now! 🚀 Please feel free to ping us if you experience any problems in the future. However, only comment if nobody has commented in the last three days or if you have information that could help us solve the problem. If there already is a recent comment or the 
@weerdy15 Thanks a lot for letting us know that this is still happening! I changed fixed to in-progress again.
In the meantime, please consider deploying your own Vercel instance to reduce server load (see github-readme-stats#deploy-on-your-own-vercel-instance). Keeping your fork up to date is just a click of a button. This process can also be automated using a GitHub action like github-repo-sync. I also added a GitHub feature request to ease the process of keeping a fork up to date (see https://github.com/github/feedback/discussions/16913).
The issue should be fixed for now as we added three new Personal Access Tokens (PATs).