Add timeouts to database creation/deletion #71
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
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.
Database creation/deletion calls should return immediately, whether successful or not. There have been timeouts, however, with no logs, that could conceivably relate to database deletion and transient network issues. These are also the only network calls left that do not have a timeout. Since there is no apparent downside, and possibly a benefit, I've added read timeouts.
This PR is inspired by log-less timeouts such as https://github.com/RelationalAI/raicode/actions/runs/5668378729/job/15359135487 - there's not a lot else to be going wrong.