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
For errors that are retryable (network, storage) we probably want to keep trying indefinitely so that a 5 minute network outage doesn't brick groups. It's better to have syncs fail for a period of time than to ignore a message that other group members might treat as valid.
Describe the solution to the problem
No response
Describe the uses cases for the feature
No response
Additional details
No response
The text was updated successfully, but these errors were encountered:
It would make sense to add a strategy field to the general Retry struct here, (to also be available on the builder) and instantiate the api client or wherever things are being retried with that strategy. A strategy could be an enum, and this one in particular be called Infinite or something. A quicker fix would just be passing usize::MAX to retries but maybe something more verbose would be appropriate. the macros would need to change accordingly to account for strategy
Is your feature request related to a problem?
For errors that are retryable (network, storage) we probably want to keep trying indefinitely so that a 5 minute network outage doesn't brick groups. It's better to have syncs fail for a period of time than to ignore a message that other group members might treat as valid.
Describe the solution to the problem
No response
Describe the uses cases for the feature
No response
Additional details
No response
The text was updated successfully, but these errors were encountered: