Closed lechuckcaptain closed 1 year ago
Hi. The 504 errors are actually being returned by GitHub's image proxy (Camo). If we can't respond with a badge within 4 seconds of GitHub's request, Camo will give up and return this error.
At the moment, it looks like there is an outage with the CocoaPods API which means CocoaPods badges are taking a long time to render because we are waiting a long time for the API response.
You'll note if you call https://trunk.cocoapods.org/api/v1/pods/SBTUITestTunnel/specs/latest (which is where the data displayed on these badges comes from), it will probably take 5-10 seconds to return a response.
Other badges appear to be rendering within the expected timeframe so I'm going to close this issue as it is a problem with an upstream API. There may be some mileage in following it up with the CocoaPods project. Cheers
Are you experiencing an issue with...
shields.io
🐞 Description
I'm getting often (not always) 504 errors on some badges of my project:
The following is the markdown generated from your website:
Some examples (1, 2, 3) of generated URLs that (at the moment) are not working.
🔗 Link to the badge
https://github.com/Subito-it/SBTUITestTunnel/blob/master/README.md
💡 Possible Solution
No response