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.

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

Deprecate retries config opt in favor of retry #422

Merged
merged 1 commit into from
Aug 16, 2023
Merged

Conversation

bdehamer
Copy link
Collaborator

Updates the Config type (exposed via the UpdaterOptions interface) to have a new fetchRetry option which supersedes the fetchRetries option.

Whereas fetchRetries only accepted a numeric value (the number of times to retry the request), fetchRetry accepts all of the options supported by the retry library which allows for more sophisticated strategies like exponential back-off.

Setting fetchRetry is still supported, but this option may be removed in a future release.

Signed-off-by: Brian DeHamer <bdehamer@github.com>
Copy link
Collaborator

@ejahnGithub ejahnGithub left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@bdehamer bdehamer merged commit d3b9587 into main Aug 16, 2023
24 checks passed
@bdehamer bdehamer deleted the bdehamer/retry branch August 16, 2023 15:31
@@ -7,7 +23,6 @@ export const defaultConfig = {
targetsMaxLength: 5000000, // bytes
prefixTargetsWithHash: true,
fetchTimeout: 100000, // milliseconds
fetchRetries: 2,
fetchRetries: undefined,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any reason we don't just cut this option in 2.0?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants