Bad Gateway errors

Hello & thanks for this fantastic service!

I’ve recently been getting more and more 502 Bad Gateway errors from badgen.net. I use badgen for the badges of cljdoc.org where I provide a static URL that people can put into their READMEs, e.g. https://cljdoc.org/badge/nrepl/nrepl.

The error page links to this https://vercel.com/docs/error/application/NO_RESPONSE_FROM_FUNCTION

To do this I’m requesting the badge from a server and then respond to the request with the body that badgen provided and some extra caching directives, the code can be found here (Clojure)

My question is:

• Do you have any idea why I might be seeing those 502 errors?
• Should I be calling the badgen API in any different way?

[wopian]

Was going to open an issue to gracefully handle 5xx responses from API providers (in this case David DM).

When these APIs return 5xx, the badge endpoint returns a HTML error page instead of a SVG which results in the following with this (https://flat.badgen.net/david/dev/wopian/kitsu) badge endpoint.

Ideally it would show something akin to

[martinklepsch]

I made some changes to get better reporting and will report back. All the URLs include the string “cljdoc” if that’s helpful.