Conversation
|
@jfudally, I think this is pretty close 👍. I have 2 x suggestions:
Lines 309 to 311 in df60fa4 So we need to do the same error catching in the looped version too (or in collectFunc itself) or this will only catch an HTTP backend being down on the first attempt
Secondly, I think we should add an error message for the Lines 21 to 37 in df60fa4 Without that the user will get a less-useful error message ( http=-1) from the fallback here: Line 67 in df60fa4 |
timvaillancourt
left a comment
There was a problem hiding this comment.
Changes suggest in last reply
|
@timvaillancourt Thanks for the review! I took care of these points you brought up. I did have some error logging, but it was pretty spammy once I caught the error out of the second call to |
|
@jfudally thanks 🎉, the latest changes LGTM! |
Related issue: #832
Description
This PR changes the default throttling behavior when using an HTTP throttler (such as https://github.com/github/freno) that is unresponsive, or returns unexpected/missing data. This change throttles gh-ost during these failure scenarios. Because this changes the existing behavior, a
--ignore-http-errorsflag was added to allow the migration to continue if the HTTP throttler goes offline.script/cibuildreturns with no formatting errors, build errors or unit test errors.