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.39k stars 692 forks source link

Streak markdown is not shown on GitHub profile #616

Open samsoncn opened 8 months ago

samsoncn commented 8 months ago

Describe the bug A clear and concise description of what the bug is: Steak Markdown is not shown on github profile

image
krios2146 commented 8 months ago

I am experiencing this issue too, but based on the message, I think it will resolve itself.

image

lakshya0310 commented 8 months ago

I am facing this issue too.

DenverCoder1 commented 8 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. If it takes too long to load, GitHub will just show a broken image instead of waiting. GitHub also caches responses on their server, so even if the speed gets back to normal, it could still show as broken on GitHub for a particular image URL for up to a few hours.

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 while hosting for over 100,000 people for free*, so self-hosting is still an option to get it to stay up more reliably.

* Scaling up to use multiple processes seems to resolve the issue but this costs about $50/month and since the project does not make any money for me and I'm not making that much from sponsorships I'd rather keep it at the lowest pricing tier. If I get at least $25/month in sponsorships, I'd keep the server scaled up.

Akash3121 commented 8 months ago

I'm facing this issue too. https://github.com/Akash3121

620

FleetAdmiralJakob commented 5 months ago

Facing same issue

Harrisbaig7 commented 5 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. If it takes too long to load, GitHub will just show a broken image instead of waiting. GitHub also caches responses on their server, so even if the speed gets back to normal, it could still show as broken on GitHub for a particular image URL for up to a few hours.

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 while hosting for over 100,000 people for free*, so self-hosting is still an option to get it to stay up more reliably.

  • Scaling up to use multiple processes seems to resolve the issue but this costs about $50/month and since the project does not make any money for me and I'm not making that much from sponsorships I'd rather keep it at the lowest pricing tier. If I get at least $25/month in sponsorships, I'd keep the server scaled up.
Harrisbaig7 commented 5 months ago

Facing same issue from past 2 days on Window Os

ZEviod commented 1 week ago

@DenverCoder1 as I noticed if you view your profile in incognito mode and see no commits for private repos , same with the streak markdown count as it will not count commit of private repo like incognito

normal mode image

and incognito mode image

so you all can try making your private repo public then it might work!