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

feat(retries): Use config params for retry parameters #1467

Merged
merged 13 commits into from
Nov 22, 2024

Conversation

PatStiles
Copy link
Contributor

Use config file for retry parameters

Description

Use config file for retry parameters

Type of change

Please delete options that are not relevant.

  • New feature

@PatStiles PatStiles changed the base branch from testnet to staging November 21, 2024 20:26
@PatStiles PatStiles force-pushed the 1401-1414-retry-config-no-jitter branch from 32f2ea3 to 1c9f3a8 Compare November 21, 2024 21:07
@uri-99 uri-99 changed the title feat(retries): Use config file for retry parameters feat(retries): Use config params for retry parameters Nov 21, 2024
core/chainio/avs_writer.go Outdated Show resolved Hide resolved
core/chainio/avs_writer.go Outdated Show resolved Hide resolved
core/chainio/avs_writer.go Show resolved Hide resolved
core/chainio/avs_writer.go Outdated Show resolved Hide resolved
core/retry_test.go Outdated Show resolved Hide resolved
core/retry_test.go Outdated Show resolved Hide resolved
core/retry_test.go Outdated Show resolved Hide resolved
core/retry_test.go Outdated Show resolved Hide resolved
core/retry_test.go Outdated Show resolved Hide resolved
core/retry_test.go Outdated Show resolved Hide resolved
@JuArce JuArce added this pull request to the merge queue Nov 22, 2024
Merged via the queue into staging with commit ffc14a2 Nov 22, 2024
3 checks passed
@JuArce JuArce deleted the 1401-1414-retry-config-no-jitter branch November 22, 2024 15:11
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.

4 participants