Skip to content
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

Maximum retries exceeded - with additional repos to pin - PAT_1 #2935

Closed
readyyyk opened this issue Jul 12, 2023 · 4 comments
Closed

Maximum retries exceeded - with additional repos to pin - PAT_1 #2935

readyyyk opened this issue Jul 12, 2023 · 4 comments
Labels
bug Something isn't working.

Comments

@readyyyk
Copy link

Describe the bug

Maximum retries exceeded
Add env variable called PAT_1 with your gh token to vercel

Expected behavior

show an image

Screenshots / Live demo link

image

Additional context

jul 12 19:15

@readyyyk readyyyk added the bug Something isn't working. label Jul 12, 2023
@rcamarano
Copy link

Hi, i've got the same problem here.
My recomendation is to make a fork form the original repo and then, deploy it on your own vercel app.
This worked very well for me.
Walktrough the tutorial on READ ME file form the original repo:
"
Deploy on your own
On Vercel
📽️ Check Out Step By Step Video Tutorial By @codeSTACKr

Since the GitHub API only allows 5k requests per hour, my https://github-readme-stats.vercel.app/api could possibly hit the rate limiter. If you host it on your own Vercel server, then you do not have to worry about anything. Click on the deploy button to get started!

Note Since https://github.com/anuraghazra/github-readme-stats/pull/58, we should be able to handle more than 5k requests and have fewer issues with downtime 😁.

Note If you are on the Pro (i.e. paid) Vercel plan, the maxDuration value found in the Vercel.json can be increased when your Vercel instance frequently times out during the card request. You are advised to keep this value lower than 30 seconds to prevent high memory usage.
"

This will make your own links for the stats so it won't broke down when the limit access was reached.

Hope that's helpful.
Cheers!

@hdaisywd
Copy link

Hi, I simply added &PAT_1 to the end of my github link and it worked for me.

@rcamarano
Copy link

Hey good to know, much simplier than deploying another project.!

@qwerty541
Copy link
Collaborator

Please check #1471. This is caused by GitHub's rate limits being reached. The only way to solve this is to deploy your own vercel instance. Adding a random string like &PAT_1 or &ANY_RANDOM_STRING_THAT_IS_NO_QUERY or changing to HTTPS works because this breaks the cache.

yenn01 added a commit to yenn01/yenn01 that referenced this issue Aug 9, 2023
Fixed readme-stats according to issue anuraghazra/github-readme-stats#2935
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working.
Projects
None yet
Development

No branches or pull requests

4 participants