Resolve import failure on very slow/unstable networks #265
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.
While working with vcs I was noticing a lot of failures when having to be on an unreliable VPN connection when running an import command. This is the failure I was seeing:
Could not determine ref type of version: kex_exchange_identification: read: Connection reset by peerAfter doing some debugging, I noted that vcs was erroring out when running the git "ls-remote" command. Upon further inspection, I noted that the retry flag was not being passed to where this command was being called. After applying the changes in this PR, vcs is now able to successfully import all my git repos on an unstable connection (with a retry flag being passed in).