search

DenverCoder1 / github-readme-streak-stats

🔥 Stay motivated and show off your contribution streak! 🌟 Display your total contributions, current streak, and longest streak on your GitHub profile README
https://streak-stats.demolab.com
MIT License
4.4k stars 692 forks source link

streak is not showing the numbers #589

Open ShorenaK opened 9 months ago

ShorenaK commented 9 months ago

Describe the bug A clear and concise description of what the bug is.

To Reproduce Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior A clear and concise description of what you expected to happen.

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

Smartphone (please complete the following information):

Additional context Add any other context about the problem here.

musagenius345 commented 9 months ago

Same issue on my bio

alin-trinca commented 9 months ago

Same issue for me too

tyronemurg commented 9 months ago

Same here

codewithastro commented 9 months ago

same

tyronemurg commented 9 months ago

Seems to be working again. Perhaps some issues on the API retreiving data

DenverCoder1 commented 9 months ago

When there is a lot of traffic to the Heroku server, the GitHub API seems to stop sending back content and the responses become very slow.

To avoid this issue, I recommend self-hosting the project. There are steps in the readme, I recently added a new method for deploying with Vercel entirely online. It's free and shouldn't take more than a couple minutes to set up.

It should also start working on its own, but there isn't much I can do to prevent it from going down in the future, so self-hosting is still an option to get it to stay up more reliably.

ShorenaK commented 9 months ago

I used vercel I m not using Heroku

On Sun, Sep 24, 2023 at 8:50 AM Jonah Lawrence @.***> wrote:

When there is a lot of traffic to the Heroku server, the GitHub API seems to stop sending back content and the responses become very slow.

To avoid this issue, I recommend self-hosting the project. There are steps in the readme, I recently added a new method for deploying with Vercel entirely online. It's free and shouldn't take more than a couple minutes to set up.

It should also start working on its own, but there isn't much I can do to prevent it from going down in the future, so self-hosting is still an option to get it to stay up more reliably.

— Reply to this email directly, view it on GitHub https://github.com/DenverCoder1/github-readme-streak-stats/issues/589#issuecomment-1732563615, or unsubscribe https://github.com/notifications/unsubscribe-auth/AX54MJS63MXRHLCIUBABMPLX4AUA5ANCNFSM6AAAAAA5ABZIWM . You are receiving this because you authored the thread.Message ID: @.***>

--

Warmest Regards

Shorena Anzhilov

LinkedIn https://www.linkedin.com/in/shorenaanzhilov/

DenverCoder1 commented 9 months ago

The main deployment linked on the repo is hosted on Heroku, but there are instructions included for those who choose to host on Vercel instead. Since my deployment gets thousands of requests every hour, it frequently reaches the limits for GitHub to send back content even with multiple tokens in use. If you host it on your own with your own GitHub token it will not be anywhere near these limits so it should not be slow or broken.