-
Notifications
You must be signed in to change notification settings - Fork 26
fix(go): retry strategy #5159
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
fix(go): retry strategy #5159
Conversation
✔️ Code generated!
📊 Benchmark resultsBenchmarks performed on the method using a mock server, the results might not reflect the real-world performance.
|
|
||
for _, h := range t.retryStrategy.GetTryableHosts(k) { | ||
// Prepare the request to be retryable. | ||
req, _ = prepareRetryableRequest(req) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like we never use the returned error. Should we avoid returning the error then?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we handle errors everywhere so I assume we can do it there as well, idk if this would lead to edge cases though
Co-authored-by: Clément Vannicatte <[email protected]> Co-authored-by: Antoine GILLES <[email protected]>
algolia/api-clients-automation#5159 Co-authored-by: algolia-bot <[email protected]> Co-authored-by: Clément Vannicatte <[email protected]> Co-authored-by: Antoine GILLES <[email protected]>
🧭 What and Why
🎟 JIRA Ticket: https://algolia.atlassian.net/browse/DI-4068
Changes included:
closes #5158