Skip to content
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.

Sign up for GitHub

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

Jump to bottom

feat: introduce a memory for retry::Policy #599

Open
wants to merge 1 commit into
base: lts/v1
Choose a base branch
from
Open

feat: introduce a memory for retry::Policy #599

wants to merge 1 commit into from

Commits on May 19, 2023

  1. feat: introduce a memory for retry::Policy 

    The idea introduced, here, is to add a "memory" parameter for the retry
policy. If a long-running retryable operation (like chainsync) fails
sporadically then the downstream oura user may not actually want the
retry counter to increment. By default, the memory should be longer than
the longest possible delay. If this isn't done then max_retries will
never be encountered and retry_operation will never return. This case
(never returning) may be desirable in some cases (like for a daemon
application). But, it should not be the default case.
    @johnrichardrinehart
    johnrichardrinehart committed May 19, 2023
    Configuration menu
    Copy the full SHA
    1af5a3f View commit details
    Browse the repository at this point in the history