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

Badges not loading on README #63

Closed
rbiggs opened this issue Feb 8, 2017 · 10 comments
Closed

Badges not loading on README #63

rbiggs opened this issue Feb 8, 2017 · 10 comments

Comments

@rbiggs
Copy link
Contributor

rbiggs commented Feb 8, 2017

Seems like shields.io has some serious latency issues. This results in the badges never loading in our README. That looks pretty unprofessional, like we don't know what we're doing. I'd suggest reducing the number of badges to reduce the latency. The Slack badge always loads, the others never. I think having the version is important so I'd suggest leading that one and the Slack one. I'm laying this issue at Shields feet because I'm noticing some serious delays on their own site as well.

@jorgebucaran
Copy link
Owner

@rbiggs I've been noticing the same thing. It's not just HyperApp, it occurs throughout GitHub consistently. I think we could eliminate the coverage badge then.

@tunnckoCore
Copy link

tunnckoCore commented Feb 8, 2017

Same here for all of my readmes. I hate that times when shields fails to do its job.

I don't think it would be "more professional" without badges. Best would be to just wait, it happens in the virtual world. :) Removing badges is not the cure and I'm against that move.

Badges are great thing and i feel bad when they not work, so I stopped working today - because of that.

@jorgebucaran
Copy link
Owner

I tried removing the coverage badge, and as you can see, it didn't really help. Only slack is okay.

@rbiggs
Copy link
Contributor Author

rbiggs commented Feb 8, 2017

So I tracked down the guy behind Shileds. Here's a Twitter feed about the current issue: badges/shields#529 (comment)

@jorgebucaran
Copy link
Owner

jorgebucaran commented Feb 8, 2017

Thanks @rbiggs. Still not clear to me what I have to do to fix this. I think I understand we'll have to wait a few weeks.

@rbiggs
Copy link
Contributor Author

rbiggs commented Feb 8, 2017

The problem is not us. It's Shields. They're having issues get the info from Github to create the badges properly. They're looking into a fix. It might come soon, or never. It's dependent on Github APIs. Sometimes Github changes that, like when the changed the API and broke the site Opensource ReportCard. So waiting is the best approach for now and see if they can resolve the issue they're having.

@tunnckoCore
Copy link

like when the changed the API and broke the site Opensource ReportCard

Heey.. yea really, that was very cool project. <3

As about the Shields... I can't get what they do with Github. I mean, i scrolled over their code base (which is very very bad), but can't remember what they do with Github and why.

In anyway, best thing is to wait some time. Most of our community relies on that project, so removing the badges isn't the right choice.

@tunnckoCore
Copy link

tunnckoCore commented Feb 9, 2017

Badges are back, hooray 💯

@jorgebucaran
Copy link
Owner

jorgebucaran commented Feb 12, 2017

Badges seem to be doing okay now. There's little we can do if their servers are busy, so let's close here.

@rbiggs
Copy link
Contributor Author

rbiggs commented Feb 12, 2017

🎉🎂🥂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants