badges / shields

Concise, consistent, and legible badges in SVG and raster format
https://shields.io
Creative Commons Zero v1.0 Universal
23.74k stars 5.5k forks source link

Travis CI invalid badges (rate limiting?) #528

Closed jakirkham closed 7 years ago

jakirkham commented 9 years ago

It appears that the repo joyent/node on GitHub was moved and renamed. However, Travis CI does not know this. So, changing the URLs for these badges is needed to fix the examples.

jakirkham commented 9 years ago

Also, seeing this for HHVM badges and MyGet.

elboletaire commented 9 years ago

Not just the examples. Mine were failing so far but whilst I write this post they appear to be ok.

Watimage build status Less CakePHP Plugin build status

Maybe is something with the cache of shields. If there are projects with a lot of movement and they're building very consecutively maybe shields shows us every time a cached image of an on-going build.

elboletaire commented 9 years ago

Maybe is something with the cache of shields. If there are projects with a lot of movement and they're building very consecutively maybe shields shows us every time a cached image of an on-going build.

Forget that. I've just seen how it changed from passing to unaccessible to passing again and I'm not currently running any build.

antonmedv commented 9 years ago

Same for me!

Mithgol commented 9 years ago

+1

kgryte commented 9 years ago

I am frequently getting inaccessible travis-ci badges. If I refresh my browser two or three times, the badge changes to success. If I leave and come back, the badge says inaccessible again. This is in contrast to the badge directly provided by travis-ci which always shows success.

espadrine commented 9 years ago

I have added a log in prod to identify what causes that. The "normal" cause is that travis does not have that repo registered, which does not seem to be the case here. So far no luck.

kgryte commented 9 years ago

The problem seemed to start, at least for me, within the past week. For an example repo, see here. If you keep refreshing, the travis-ci badge will randomly alternate between inaccessible and success.

espadrine commented 9 years ago

Here is what I have: sometimes, Travis CI returns {"file":"not found"}, sometimes, Retry later, when downloading their badge. Is that a rate-limiting thing?

espadrine commented 9 years ago

Historically, we request badges instead of using the API because the straightforward API queries sometimes produce "pending", which is not a badge people ever want to see, and some other way to use the API to circumvent that had issues when dealing with branches. People wanted our badges to show the same information as the Travis CI badges (with the customizability that we offer).

I have gone full circle, and switched it to only perform a HEAD request, on the SVG headers this time. Let me know if it changes anything.

bcomnes commented 9 years ago

Seeing a lot of invalid travis badges this morning.

TomasVotruba commented 9 years ago

Same here:

ankitpokhrel commented 9 years ago

Same problem here!

Mithgol commented 9 years ago

It seems to me that the problem's gone. Is it a weekend's effect, I wonder.

JayBizzle commented 9 years ago

Still seeing the Invalid Travis badges

netvl commented 9 years ago

Indeed, I have the same problem. Shields.io: (https://img.shields.io/travis/netvl/xml-rs.svg?style=flat-square) Travis: (https://travis-ci.org/netvl/xml-rs.svg?branch=master)

Occasionally the shields badge becomes green but usually it is invalid.

elboletaire commented 9 years ago

I currently see them better than before the change. It's true that now they appear as "invalid" sometimes but it's less often than when they said "inaccessible".

brianreavis commented 9 years ago

Also getting a bunch of Invalid badges across many repos.

artem-malko commented 9 years ago

+1

paulmelnikow commented 7 years ago

If this problem recurs, feel free to open a new issue.