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

incorrect error for messages #5312

Closed
netuwu opened this issue Aug 13, 2022 · 4 comments
Closed

incorrect error for messages #5312

netuwu opened this issue Aug 13, 2022 · 4 comments
Labels

Comments

@netuwu
Copy link

netuwu commented Aug 13, 2022

Description

the error message is incorrect

Steps to Reproduce

send enough messages in a channel to get yourself rate-limited

Expected Behavior

"message": "You are being rate limited."

Current Behavior

message: "The write action you are performing on the channel has hit the write rate limit."

Screenshots/Videos

image

Client and System Information

Canary 141389 (f0f2e03)
Windows 10 64-Bit (10.0.19043)

@netuwu netuwu added the bug label Aug 13, 2022
@advaith1
Copy link
Contributor

that’s not a bug

@netuwu
Copy link
Author

netuwu commented Aug 13, 2022

What is it then? Why does it do that in the first place?

@wasdennnoch
Copy link
Contributor

It's a channel-global rate limit shared by all users sending messages in that channel, rather than a rate limit just for your client, hence the different message to make that distinction clear. Your own rate limit may not be exhausted yet, but the channel-global limit is.

@Jupith
Copy link
Contributor

Jupith commented Aug 13, 2022

It's a channel-global rate limit shared by all users sending messages in that channel, rather than a rate limit just for your client, hence the different message to make that distinction clear. Your own rate limit may not be exhausted yet, but the channel-global limit is.

True but it's also sent when a single user hits the channel send limit for themselves.

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

No branches or pull requests

5 participants