🌱 When Robot API reaches a timeout, retry later. #1639
Conversation
This file contains hidden or 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
github-actions
bot
added
size/XS
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.
When Robot API reaches a timeout, retry later
The Robot API of Hetzner returned this:
We do want to retry N seconds later. Up to now the provisioning process was stopped and started from scratch.
TODO
Maybe it is best, if we join the rate-limit handling with timeout handling into one method, so that we do not have too many similar lines after each robot-api call.
But how to check for all kind of network errors (dns timeout, dns resolve failed (name to ip), network unreachable, connection refused, ....)?