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

Introduce RetriesDefaultWaitTime #219

Closed

Conversation

marbra-dev
Copy link

No retries will be performed in case of a 429 response does not include a Retry-After header.
This PR adds a new default wait time, which can be set to perform retries.

No retries will be performed in case of
that the 429 response does not include a
"Retry-After" header. The PR adds a new default
wait time, which can be set to perform retries
@marbra-dev marbra-dev marked this pull request as ready for review July 8, 2024 11:45
@marbra-dev marbra-dev marked this pull request as draft July 8, 2024 15:51
@marbra-dev marbra-dev marked this pull request as ready for review July 8, 2024 16:59
@stephenfin stephenfin self-requested a review July 17, 2024 15:44
@pierreprinetti
Copy link
Contributor

I don't think that we should ship generic retry functions in Gophercloud. A retry mechanism can be implemented on the consumer side, possibly by using any of the specialised libraries on the Net.

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.

2 participants