search

badges / shields

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

Discord Badge has rate limit error #10223

Open cech12 opened 5 months ago

cech12 commented 5 months ago

Are you experiencing an issue with...

shields.io

🐞 Description

I am using your shields.io service to generate Discord badges for my Discord server. But since some days the badge looks like that: grafik I don't know what I am doing wrong or if this is an issue on your side. Thanks for your help! :)

🔗 Link to the badge

https://img.shields.io/discord/752506676719910963.svg?style=flat&color=informational&logo=discord&label=Discord

💡 Possible Solution

No response

github-actions[bot] commented 5 months ago

Badge tested using npm run badge https://img.shields.io/discord/752506676719910963.svg?style=flat&color=informational&logo=discord&label=Discord Output is available here

chris48s commented 5 months ago

We've been occasionally hitting the discord rate limits for some time. We've been tracking this in https://github.com/badges/shields/issues/9862 but it has been quite a limited issue

However, in the last few days we seem to have had a huge increase in the number of 429 calling https://discord.com errors:

Screenshot at 2024-06-06 20-00-47

As far as I can see from the metrics we haven't had a huge increase in the number of badges being requested so I think something has changed upstream. Maybe the rate limit on our token has been massively decreased. @PyvesB - is the token attached to your account? Do you have any visibility on this?

PyvesB commented 5 months ago

As far as #9862 is concerned, the last I heard from our point of contact at Discord was that he was working on identifying the team owning the rate limiting capabilities internally. However, it's been a while since I last heard from him, I've followed up linking to this new issue. Will keep you posted when I get his response.

Xuanwo commented 5 months ago

However, it's been a while since I last heard from him, I've followed up linking to this new issue. Will keep you posted when I get his response.

Thanks a lot for your effort.

waydabber commented 5 months ago

Hope this will be resolved! :)

TriForceX commented 5 months ago

As a workaround ive made a little PHP script that uses the custom shields badge text in conjunction with Discord widget API to make the same behaviour. (You have to host it yourself)

Use this as: http://yourwebsite.com/badge.php?id=yourserverid

Heres a working example: discord

Heres the code: https://gist.github.com/TriForceX/a8332709718851ea1bf0cad15f3a2600

PS: Ive used get method to allow more ids to be added, but it can be modified.

Burhan-Q commented 4 months ago

We are also seeing this issue with our Discord badges at Ultralytics and it would be great to have a resolution to this, otherwise we'll have to find a replacement badge to use in our repos and docs pages.

tillrohrmann commented 4 months ago

We observe the same problem with our Restate repositories.

PyvesB commented 4 months ago

I've sent another follow up mail. I received one out of office automated response, and one response saying they'll escalate tomorrow. Fingers crossed 🤞🏻

syorito-hatsuki commented 4 months ago

Same here in all my README

cbartondock commented 4 months ago

Also seeing this issue with SteamGridDB repositories, the badge has been in a non working state continuously as far as I can tell.

revi commented 4 months ago

People might want to check out NoPlusOne from go wiki. (Of course, The project admins will delete such comments as a matter of procedure (please don’t be offended if we delete yours). won't apply as this is not go project and I don't have the permission necessary to do it on this repo)

chris48s commented 4 months ago

We are already aware this is affecting 100% of users.

I've locked this issue due the "plus 1" comments. I think that this stage allowing anyone to comment on this issue is unhelpful.

Please feel free to subscribe to the issue for updates. We will continue to update once we know something.

PyvesB commented 4 months ago

The full outage got resolved a few days ago. I'm still trying to figure out with the Discord team what may have happened, I'm presently unclear on what triggered this incident in the first place, and what resolved it.

We're still getting occasional small spikes of errors, essentially what was reported in #9862. I've reiterated our request to update our rate limits.

PyvesB commented 2 months ago

I've reiterated our request to update our rate limits.

Unfortunately, I've not heard back, even after following up again in the meantime.