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

Standardize retry and timeout semantics #30

Open
lblackstone opened this issue Jun 2, 2022 · 0 comments
Open

Standardize retry and timeout semantics #30

lblackstone opened this issue Jun 2, 2022 · 0 comments
Labels
kind/enhancement Improvements or new features

Comments

@lblackstone
Copy link
Member

Each provider currently handles failure retries and operation timeouts differently (or not at all). Both of these should be standardized and handled in a single place in the provider to make it easier to explain and debug related failure cases.
@lblackstone lblackstone added the kind/enhancement Improvements or new features label Jun 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/enhancement Improvements or new features
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@lblackstone