-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mgit2 bootstrap should try for the second time if the repo fail #87
Comments
Good idea! |
Does a 5 seconds delay between the first and the second try sound good? |
I hope so :) |
I think that the question is – does it help? |
The problem is that it's only reproducible on @pjasiun's macs 😄 |
I am not able to reproduce it but I am still trying. |
Yep. You're right. I've just hit this error twice right now in the office. And it doesn't happen when I'm working from home. |
Does the solution described here – https://stackoverflow.com/questions/6842687/the-remote-end-hung-up-unexpectedly-while-git-cloning – help? Could you test it? |
Feature: Introduced a mechanism which allows executing the `bootstrap` command once again if it ends with an error. Closes #87.
I still get this error randomly when execute
mgit bootstrap
and if it is part of the bigger task, likeyarn reset
or docs building it breaks the whole flow badly, force me to fix the structure manually.Since we have no idea how to fix this error, I think we should make mgit try again in such cases, probably with some timeout. I believe this is because we reach the number of simultaneous connections to github.
The text was updated successfully, but these errors were encountered: