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

All stats card and repo features are down. Error cannot fetch user is shown on all cards including your readme #bug #51

Closed
ApurvShah007 opened this issue Jul 14, 2020 · 57 comments · Fixed by #58
Labels
bug Something isn't working. help wanted Extra attention is needed.

Comments

@ApurvShah007
Copy link

No description provided.

@ApurvShah007 ApurvShah007 changed the title All stats card and repo features are down. Error cannot fetch user is shown on all cards including your readme All stats card and repo features are down. Error cannot fetch user is shown on all cards including your readme #bug Jul 14, 2020
@filiptronicek
Copy link
Contributor

Same here, too.

@filiptronicek
Copy link
Contributor

Probably hit the API limit.... @ApurvShah007

@ApurvShah007
Copy link
Author

@anuraghazra Is there any possible solution? I really like this feature and I am down to help fix this issue. @filiptronicek Thats probably what happened

@anuraghazra
Copy link
Owner

Github API limit is hit. it should be up in some time

@anuraghazra
Copy link
Owner

It's really a bummer that github api only allows 5k requests per hour. sorry guys i'll see what i can do to fix the issues.

@ApurvShah007
Copy link
Author

@anuraghazra That is a bummer, how do you plan to fix it? Will it fix itself?

@anuraghazra
Copy link
Owner

It will fix itself after a window of time, but i'm working on a proper fix so that it should not happen too often

@filiptronicek
Copy link
Contributor

But it is just a temporary solution, I think there is just one solution: delete the Vercel project, don't let anyone use it, and force everyone to use their self-hosted version with their own PAT.

@anuraghazra
Copy link
Owner

anuraghazra commented Jul 14, 2020

@ApurvShah007
Copy link
Author

@filiptronicek I was about to suggest the same thing, I am pretty sure everyone can host their own requests making it self-sufficient.

@filiptronicek
Copy link
Contributor

I know, I host one myself, but I would make it mandatory, it isn't very wise to encourage people to use something, that doesn't work a lot of the time. This project just doesn't scale well, although it is an awesome tool!

@anuraghazra
Copy link
Owner

Yup i agree. i might migrate to doing that, but i'm currently experimenting with caching and collaborating with @statically.io to see what would work best.

@ApurvShah007
Copy link
Author

@filiptronicek and @anuraghazra am I supposed to deploy it on the repo that exists or should I make a new one? I am kind of a boomer sorry.

@anuraghazra
Copy link
Owner

you can fork this repo and click on the deploy button after that generate your github personal token and use put it on vercel

@filiptronicek
Copy link
Contributor

I suggest you fork the repo, and set up Vercel with that repo because then you can always update your own

@filiptronicek
Copy link
Contributor

Talking of the self-hosted version, any idea why I have an A++ ranking on the official site, but in my own instance, I have a ranking of just A+, nothing, that would anger me or something, but it still is weird. @anuraghazra

@ApurvShah007
Copy link
Author

ApurvShah007 commented Jul 14, 2020

@anuraghazra @filiptronicek do I allow it to install on all my repos?

@filiptronicek
Copy link
Contributor

Yes, I would suggest you do, for future usage, but if you don't plan on using it, just install it on the one fork @ApurvShah007

@ApurvShah007
Copy link
Author

@filiptronicek Well I plan to have the GitHub readme stats card and feature a few repos on my profile readme. IDK what I should do

@filiptronicek
Copy link
Contributor

Just allow all repos then, will be easier @ApurvShah007

@filiptronicek
Copy link
Contributor

Another idea @anuraghazra, we could implement multiple PATs like this:
try request with PAT_1.... fail
try request with PAT_2....fail
try request with PAT_3....sucess

We could handle 50K request with just 10 tokens, every hour

@ApurvShah007
Copy link
Author

Is it back up for everyone or did I set up my Vercel correctly?

@filiptronicek
Copy link
Contributor

It is back up @ApurvShah007

@anuraghazra
Copy link
Owner

anuraghazra commented Jul 14, 2020

Talking of the self-hosted version, any idea why I have an A++ ranking on the official site, but in my own instance, I have a ranking of just A+, nothing, that would anger me or something, but it still is weird. @anuraghazra

Yup there is some issues with ranking system its currently biased, checkout #41 #49 for more info.

@ApurvShah007
Copy link
Author

Ok I still want to set up mine properly. I let it install on all my repos and the project is up on Vercel

@anuraghazra
Copy link
Owner

anuraghazra commented Jul 14, 2020

Another idea @anuraghazra, we could implement multiple PATs like this:
try request with PAT_1.... fail
try request with PAT_2....fail
try request with PAT_3....sucess

We could handle 50K request with just 10 tokens, every hour

@filiptronicek

What are PATs?

Can we do that? like each github personal token would have its own 5k limit?

@ApurvShah007
Copy link
Author

ApurvShah007 commented Jul 14, 2020

@filiptronicek @anuraghazra I feel like you should make a guide on how to set up the while thing. Specially for people like me

@filiptronicek
Copy link
Contributor

Another idea @anuraghazra, we could implement multiple PATs like this:
try request with PAT_1.... fail
try request with PAT_2....fail
try request with PAT_3....sucess
We could handle 50K request with just 10 tokens, every hour

@filiptronicek

What are PATs?

Can we do that? like each github personal token would have its own 5k limit?

PATs are personal access tokens, if we had more, we could do more requests

@anuraghazra
Copy link
Owner

@filiptronicek @anuraghazra I feel like you should make a guide on how to set up the while thing.

Yup i'll do it tomorrow got 3 same questions today.

@anuraghazra anuraghazra added bug Something isn't working. help wanted Extra attention is needed. labels Jul 14, 2020
@filiptronicek
Copy link
Contributor

Ok, so @anuraghazra
github api docs
We could just gather 10 users to get 10 different user PATs!

@ApurvShah007
Copy link
Author

ApurvShah007 commented Jul 14, 2020

@filiptronicek I don't mind being one user if you ever need it. Just let me know what to do.

@garvit-joshi
Copy link

@filiptronicek @anuraghazra, count me in.

@anuraghazra
Copy link
Owner

Sounds great 😃 @ApurvShah007 @garvit-joshi thanks for the support, I highly appreciate it.

Can you guys leave your Twitter so that I can contact you about this.

@ApurvShah007
Copy link
Author

@anuraghazra I don't have a twitter we can do LinkedIn or Insta too if that works

@anuraghazra
Copy link
Owner

@ApurvShah007 insta would work 😃

@garvit-joshi
Copy link

garvit__joshi

@ApurvShah007
Copy link
Author

https://www.instagram.com/apurvshah007/

@filiptronicek
Copy link
Contributor

@filiptronicek on Twitter @anuraghazra

@ApurvShah007
Copy link
Author

@anuraghazra I followed you back in insta

@filiptronicek
Copy link
Contributor

I can do it today, and make a PR @anuraghazra

Of course, please ❤️

#53

@infinity-plus
Copy link

Can we not add a clause that fetches new updates every 24 hours and use the image obtained for whole day? Just a suggestion, I'm noob.

@anuraghazra
Copy link
Owner

@infinity-plus 24 hours Is a bit much, I think you would like the stats to be frequently updated. Currently I have 5min cache setup, so I'll fetch new data every 5min

@infinity-plus
Copy link

@anuraghazra I don't think anybody checks my git every 5mins tho, + this repo is getting popular
Maybe 1 hr?

@ApurvShah007
Copy link
Author

@anuraghazra The live number of visitors is also dead. Not sure if I took it from your repo or not but do you have any idea?

@anuraghazra
Copy link
Owner

@anuraghazra The live number of visitors is also dead. Not sure if I took it from your repo or not but do you have any idea?

No there is no relation with that thing whatsoever.

@ApurvShah007
Copy link
Author

@anuraghazra visitors is the link I am using. Any idea why its down?

@TheAshwanik
Copy link

@anuraghazra The live number of visitors is also dead. Not sure if I took it from your repo or not but do you have any idea?

Yes. It hit the rate limit too.
I had to deploy my own instance.. similar to this one.

@garvit-joshi
Copy link

@TheAshwanik , acc. to my understanding the issue has been fixed, PAT have been increased, I am using the original instance and it works fine.

@TheAshwanik
Copy link

@TheAshwanik , acc. to my understanding the issue has been fixed, PAT have been increased, I am using the original instance and it works fine.

@garvit-joshi I was talking about the "live number of visitors"
This one: https://visitor-badge.glitch.me/badge?page_id=xxxx

@ApurvShah007
Copy link
Author

@TheAshwanik I would also like to deploy my own so I dont run into the same problem. It would be helpful if you can make a short tutorial on that.

@TheAshwanik
Copy link

@TheAshwanik I would also like to deploy my own so I dont run into the same problem. It would be helpful if you can make a short tutorial on that.

Will do..

@anuraghazra
Copy link
Owner

@ApurvShah007 @TheAshwanik can you guys continue the discussions regarding visitor badge here: https://github.com/jwenjian/visitor-badge

It's the official repo, please open an issue there.

Since this repo does not have any connection with visitor badge I think it's not the right place to discuss it. Otherwise you can always hop into my discord server if you have any issues. Thanks!

@ApurvShah007
Copy link
Author

@anuraghazra Sorry about that. I would love a link to your discord.

@anuraghazra
Copy link
Owner

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working. help wanted Extra attention is needed.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants