-
Notifications
You must be signed in to change notification settings - Fork 6
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
Rate Limit Exceeded #12
Comments
Are you on 0.3.6? I fixed some ratelimit-related issues in the latest update. If not, try updating and let me know if you still run into this. |
Yes, it is 0.3.6. |
Got it, can you try 0.3.7-beta.0 and see if this continues to happen? |
Still happening
|
Weird, I'll have to see if I can reproduce. |
Can you give beta.1 a shot? Apologies, this is tough to pin down. |
Fix is published in 0.3.7, let me know if you continue to run into this. |
Happened again
Version was 0.3.7-beta.1, but it's the same right? |
Weird, the headers indicate you've still got 2950 requests remaining. What's the other process running on your server (i.e. is it also running @skyware bot? Is it only using chat endpoints or others as well?) |
it's running in my house so the other client would be me using the bluesky chat |
Actually, I'm on a different network with different IP so it must be just the bot but it still happens. I'm using .sendMessages() with more than a dozen people, could it be that this rate limit is for the individual messages and not the HTTP requests? https://gitea.moe/lamp/bluesky-groupchat-bot/src/commit/da34c1012123a6f8d536a24625eec1d8b5cad975/index.mjs#L97 |
That's a timestamp, not a length of time. Really not sure though, my best guess is that the chat service has its own rate limits that aren't actually being exposed — will need to ask about it. |
Thought this library was supposed to handle rate limits but I got "Failed to send message(s)." errors after using bot.sendMessages() a bunch of times.
The text was updated successfully, but these errors were encountered: