-
Notifications
You must be signed in to change notification settings - Fork 24
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
Bug - rake geocombine:clone errs out #144
Comments
Can you do a full trace? I wonder if this is being thrown from the ruby git client or something. I think I might've seen it once or twice when testing but I haven't managed to replicate it recently. |
Saw the same issue, when trying to execute Cloging only edu.nyu worked Working on Ubuntu 22.04 with these versions:
|
Providing both `directory` and `path` to Git.clone results in the repo being cloned into a directory nested inside itself. This may be a fix for #144.
Providing both `directory` and `path` to Git.clone results in the repo being cloned into a directory nested inside itself. This may be a fix for #144.
Thanks for the trace — I think this might've been related to arguments I was passing to It could also be related to the behavior that happens when we try to clone a Git repository with no contents (of which there are a few in OGM); #139 has better behavior to handle that. Unfortunately PRs are failing because a new rubocop is angry about one of our tests being skipped without a reason; #147 fixes that issue. |
Providing both `directory` and `path` to Git.clone results in the repo being cloned into a directory nested inside itself. This may be a fix for #144.
3f4389e removes the recursion which I think might've been the cause of this. |
This is fixed! I was able to clone all the repos...
|
I've been playing around with GeoCombine for Aardvark metadata harvesting.
Harvesting individual institutions has been working well:
But cloning all the repos, fails:
First run
Second run
Can anyone else confirm? Seems to likely StackError the same place each clone run...
The text was updated successfully, but these errors were encountered: