adds retry mechanism on network failures #97
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Vadorequest
requested changes
May 26, 2023
Closed
|
PR migrated to #98 |
Vadorequest
added a commit
that referenced
this pull request
May 26, 2023
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
👋 Thanks for making this action. We have been using it quite a bit in a high throughput environment.
We have ran into some issues with the Vercel API so we added a simple retry mechanism to avoid failing our CI checks. We've been running it for a few months and it helped stabilize our pipeline.
I tried to find the most compatible retry library to be as "drop-in" as possible.