Skip to content
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

terra e:enable: Unable to clone repository. Check app settings and try again. #79

Open
jlyon opened this issue Aug 10, 2015 · 5 comments
Labels

Comments

@jlyon
Copy link
Contributor

jlyon commented Aug 10, 2015

I have been trying to enable an app with a large repo (1gb) and I am getting this error:

Unable to clone repository. Check app settings and try again.

Oddly enough, it looks like the repo is getting cloned properly (and completely). If I run terra e:enable again the env gets enabled and all is well.

@jonpugh
Copy link
Member

jonpugh commented Aug 10, 2015

might be timing out?

@jlyon
Copy link
Contributor Author

jlyon commented Aug 10, 2015

yeah, i think maybe the php script is timing out or something? the full repo does get cloned. I've had similar issues with other smaller repos on my localhost.

@jonpugh
Copy link
Member

jonpugh commented Aug 12, 2015

Hmm... Since we use https://github.com/cpliakas/git-wrapper it is really in their code...

We call "clone" at https://github.com/terra-ops/terra-cli/blob/master/src/terra/Factory/EnvironmentFactory.php#L85

That error is from our code and is really dumb... we need better exceptions thrown there.

Let's dig in and figure out what is really causing the problem.

Can you post additional error messages right before that one?

We can also look into if the git-wrapper uses symfony Process and setTimeout(null).

@asgorobets
Copy link
Contributor

GitWrapper has a timeout of 60 seconds if not specified otherwise.
We might want to modify this timeout for terra, as GitWrapper is configurable to do that.

For example:

$wrapper = new GitWrapper();
$wrapper->setTimeout($this->getTimeout());

@kynetiv
Copy link

kynetiv commented Mar 11, 2016

Just wanted to share I ran into this where cloning was taking too long for whatever reason. I thought I might just clone it myself somewhere and let environment:add know the path to the cloned copy but then ran into the reverse error that:

Git clone already exists at that path, but it is not for this app.

As a workaround I ended up just manually adding the environment to the ~/.terra/terra file and it was fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants