-
Notifications
You must be signed in to change notification settings - Fork 15
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
Handling/retrying transient network failures #64
Comments
Hi @franklad! Sorry for getting back to you late, we are certainly open to ideas to make Merge Gatekeeper more resilient and reliable! It makes sense to handle some transient errors by retrying them, and we would definitely look more closely 👍 |
Added this PR: #67. Let me know what you think, happy to make changes. |
@franklad you mentioned network issues Thanks for the pr! |
Hey @omer2500, sorry for the late response. They return 400s afaik |
Hi everyone,
Sometimes when
merge-gatekeeper
tries to call GitHub API, GitHub returns 5xx errors or EOF and they tend to be all transient network errors.Would you be open to adding retries to GitHub API calls? I'm happy to discuss more and add the functionality.
Initial thoughts were adding retry flag to the cli and adding a retry roundTripper to the GitHub client.
The text was updated successfully, but these errors were encountered: