-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Add retries for more network related errors #3957
Add retries for more network related errors #3957
Comments
Jan 9 2020 TPG run has a few examples of "read: connection reset by peer" in case anyone needs debug logs for a failure |
Some tests were fixed, but I think various libraries are still returning weird error formats, keeping open to track removing debug logs from a fix |
Moving to near-term goals, since it will most likely get fixed by #5460 |
@emilymye what work (if any) is remaining for this? |
This was just open to see if we ran into more network errors - since we pretty much don't get them now unless there's a big outage, I'm going to close |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks! |
Community Note
Errors like these pop up every so often in tests and bug reports:
We should probably consider these retryable, or hard-code in a certain number of tries, since there's not much a user can do about them besides just try again.
The text was updated successfully, but these errors were encountered: