-
When there is a failure, `-repeat` retries. That's fine, but retrying every 10s forever is not ok. Just like mail delivery, repeat should have some kind of backoff. Exactly what is not critical, …
-
I think it would be great for the bot to operate with [exponential backoff](https://www.wikiwand.com/en/Exponential_backoff), so as to not bother the authors of issues that are expected to take a long…
-
As @mreiferson pointed out, we should implement the [backoff](http://bitly.github.io/nsq/clients/building_client_libraries.html#backoff) mechanism for failed job processing.
-
I'm loving this set of components, but I frequently run into "User Rate Limit Exceeded" quota errors. I've implemented Exponential Backoff for retrying requests but I think it would be great if this f…
-
A more diverse crawl policy.
-
Whenever you make HTTP requests, there are plenty of completely valid reasons for the request to not complete:
From [this book](https://www.safaribooksonline.com/library/view/http-the-definitive/1565…
-
I am currently developing a WFSA language model. I have just started using K2, and I am struggling with implementing the back-off language model.
My model is fully connected (which means that fo…
Banaf updated
2 years ago
-
Would be great to get exponential backoff built into our client such that any requests which return 5xx errors get retried automatically -- this would improve client app stability as any bad requests …
-
Add an algorithm used to space out repeated retries
-
### Describe the bug
- Langfuse leads to `Giving up execute_task_with_backoff(...) after 3 tries (httpx.ReadTimeout: timed out)
Giving up execute_task_with_backoff(...) after 3 tries (httpx.ReadTime…