python-zulip-api
python-zulip-api copied to clipboard
zulip
Handle `RATE_LIMIT_HIT` (Rate limit exceeded) errors
It would be nice if this library handled RATE_LIMIT_HIT errors automatically by sleeping for retry-after seconds and retrying the request. Otherwise this logic needs to be implemented in every user application.
Welcome to Zulip, @Fahdmoh01! We just sent you an invite to collaborate on this repository at https://github.com/zulip/python-zulip-api/invitations. Please accept this invite in order to claim this issue and begin a fun, rewarding experience contributing to Zulip!
Here's some tips to get you off to a good start:
- Join me on the Zulip developers' server, to get help, chat about this issue, and meet the other developers.
- Unwatch this repository, so that you don't get 100 emails a day.
As you work on this issue, you'll also want to refer to the Zulip code contribution guide, as well as the rest of the developer documentation on that site.
See you on the other side (that is, the pull request side)!
@i-ky does the Rate limit has to do with the message_limit?
Sorry, I am not familiar with Zulip's internals. What is message_limit you are talking about?
@i-ky does the Rate limit has to do with the message_limit?
Sorry, I am not familiar with Zulip's internals. What is
message_limityou are talking about?
message_limit is a variable inside the Ratelimit class of the zulip python api. where do I go to ask for further clarification for this issue?
I can only clarify what I propose to be changed from a python-zulip-api user's perspective, how it is to be changed from python-zulip-api perspective is a different matter.
This need to be done as an option -- some clients might very much not want to have sleeps of this form be part of what might happen.
I suppose there's also a question of whether we want the semantics to be to automatically retry the operation that failed due to the rate limit, or something else.
We also need to be cautious in implementing documenting this sort of thing to make sure we don't end up with bugged clients hitting the server exactly as often as the rate limits allow - that can generate a lot more useless load than something that doesn't retry. Probably this is not too hard to manage.
@Fahdmoh01 You have been unassigned from this issue because you have not made any updates for over 14 days. Please feel free to reclaim the issue if you decide to pick up again. Thanks!
@timabbott Hi, is this issue still up for grabs and is it something that I can start working on...
Welcome to Zulip, @quinnah! We just sent you an invite to collaborate on this repository at https://github.com/zulip/python-zulip-api/invitations. Please accept this invite in order to claim this issue and begin a fun, rewarding experience contributing to Zulip!
Here's some tips to get you off to a good start:
- Join me on the Zulip developers' server, to get help, chat about this issue, and meet the other developers.
- Unwatch this repository, so that you don't get 100 emails a day.
As you work on this issue, you'll also want to refer to the Zulip code contribution guide, as well as the rest of the developer documentation on that site.
See you on the other side (that is, the pull request side)!
i tried sending a lot of messages in a loop but it seems to handle it well already
@codewithnick, try a different API endpoint (e.g. I originally suffered from it while uploading custom emojis). I would assume that Zulip is quite tolerant to bursts of messages sent, but may use stricter limits for other stuff.
Or try harder using multiprocessing/threading/asyncio :wink:
tried using custom emojis it all looks the same
I think it is use less to make it any faster even if it fails on multithreads, because then you are basically abusing the api
@codewithnick, you can also try lowering limits for your Zulip server.
is there any way to do it? pl lmk
@codewithnick, you can also try lowering limits for your Zulip server.
is there any way to do it? pl lmk
I believe this is the relevant piece of documentation.
Hello @avijitdas126, it looks like you've currently claimed 1 issue in this repository. We encourage new contributors to focus their efforts on at most 1 issue at a time, so please complete your work on your other claimed issues before trying to claim this issue again.
We look forward to your valuable contributions!
Welcome to Zulip, @pranavrockz! We just sent you an invite to collaborate on this repository at https://github.com/zulip/python-zulip-api/invitations. Please accept this invite in order to claim this issue and begin a fun, rewarding experience contributing to Zulip!
Here's some tips to get you off to a good start:
- Join me on the Zulip developers' server, to get help, chat about this issue, and meet the other developers.
- Unwatch this repository, so that you don't get 100 emails a day.
As you work on this issue, you'll also want to refer to the Zulip code contribution guide, as well as the rest of the developer documentation on that site.
See you on the other side (that is, the pull request side)!