This repository was archived by the owner on Apr 25, 2024. It is now read-only.
Increasing timeouts for repository check #23
Merged
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
Slow responding repositories were marked with a repository failure because of the low read timeout value. Increases the timeout for the repository check.
Member
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
We have a problem with repositories with slow response times (proxy server in between that additionally slows the responses). We get failure icons in the web application for these repositories because of the relatively low hardcoded read timeout value.
The patch increases the timeout for the repository check and adds getter / setter for the values. Maybe it would be better to make the values configurable, but would like to keep the patch small and put this for discussion.