mgit2 bootstrap should try for the second time if the repo fail

[pjasiun]

I still get this error randomly when execute mgit bootstrap and if it is part of the bigger task, like yarn 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.

[Reinmar]

Good idea!

[pomek]

Does a 5 seconds delay between the first and the second try sound good?

[pjasiun]

I hope so :)

[Reinmar]

I think that the question is – does it help?

[ma2ciek]

The problem is that it's only reproducible on @pjasiun's macs 😄

[Reinmar]

And @scofalik's :> But perhaps it can be generalised to our hq's network. If you won't be able to reproduce it with 40+ repositories, ping guys there to try to check it, @pomek.

[pomek]

I am not able to reproduce it but I am still trying.

[ma2ciek]

And @scofalik's :> But perhaps it can be generalised to our hq's network. If you won't be able to reproduce it with 40+ repositories, ping guys there to try to check it, @pomek.

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.

[pomek]

Does the solution described here – https://stackoverflow.com/questions/6842687/the-remote-end-hung-up-unexpectedly-while-git-cloning – help? Could you test it?