You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am a heavy user of gh-got as part of renovate. A small percentage of request receive a 502 Bad Gateway response and it's pretty obvious that these should be retried somewhere in the stack rather than bailing and stopping all subsequent processing.
I was going to write a wrapper around gh-got to achieve this but then thought I'd open an issue here for discussion first as it seems like something all users of gh-got would benefit from and not specific to my application.
Thanks for the feedback and pointer to p-retry. What I plan to do is incorporate a p-retry wrapper within my application first and observe its results for a while before proposing the enhancement into gh-got here.
I am a heavy user of
gh-got
as part of renovate. A small percentage of request receive a502 Bad Gateway
response and it's pretty obvious that these should be retried somewhere in the stack rather than bailing and stopping all subsequent processing.I was going to write a wrapper around
gh-got
to achieve this but then thought I'd open an issue here for discussion first as it seems like something all users ofgh-got
would benefit from and not specific to my application.Relevant thread there: sindresorhus/got#199 (kind of dismissing the idea).
Additionally: I do not need stream support
The text was updated successfully, but these errors were encountered: