You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since the default behavior has an incremental delay, this combined with asynchronous promises, usually means after a few promises fail for a few times, they are kept in the stack until the number of retries ends.
This is great, but I'd like to suggest a feature for extreme cases. I have a websocket that receives a lot of events, and some of them might take some processing time that could go up to an hour or two. Could there be a pooling feature to limit the total amount of pending retries? So once the number of promises reaches a maximum, the earliest one gets discarded and so-on.
Or if not possible, maybe just a way to stop retries for a promise depending on the argument that was passed to it, and leave handling them or pooling them depending on each dev's usecase.
The text was updated successfully, but these errors were encountered:
Since the default behavior has an incremental delay, this combined with asynchronous promises, usually means after a few promises fail for a few times, they are kept in the stack until the number of retries ends.
This is great, but I'd like to suggest a feature for extreme cases. I have a websocket that receives a lot of events, and some of them might take some processing time that could go up to an hour or two. Could there be a pooling feature to limit the total amount of pending retries? So once the number of promises reaches a maximum, the earliest one gets discarded and so-on.
Or if not possible, maybe just a way to stop retries for a promise depending on the argument that was passed to it, and leave handling them or pooling them depending on each dev's usecase.
The text was updated successfully, but these errors were encountered: