importing more than 20 repos causes fails
See original GitHub issueHi, I am using latest version of the vcstool (0.1.20). I have a YAML file consisting more than 35 repos. When I try importing repos to a single folder after 20~ repos it is throwing errors and stuck downloading next repos. I have tried splitting YAML file to 3 different files and running them in order to same folder. Every one of them has around 12 repos. First one goes without problem but second one either throws error or stuck downloading. I am able to clone all the repos manually meaning that there is no permission issue.
I get something like this :
.....................EE..EE....
Issue Analytics
- State:
- Created 7 years ago
- Comments:9 (6 by maintainers)
Top Results From Across the Web
Import Fails with missing content and 13 ... - GitLab
This points to a memory issue. The worker got killed and then it retried, failing that second time because most of our imports...
Read more >Why Gitlab fails importing repository from local network with ...
Every import attempt has failed: Error importing repository http://111.222.33.44/path/to/my/repository/root/folder/.git into myuser/my_project - ...
Read more >Configured repository, but failed to import resource from ...
Configured repository, but failed to import resource from workspace, this could happen if there are invalid resources. Details: undefined.
Read more >Repository Import Fails · Issue #772 · education/classroom
When students import a repository, that import may fail and leave their repository in an unworkable state. The workaround seems to be for ......
Read more >"ODI-14070: Import Failed. The Parent Object Was Not Found ...
The Parent Object Was Not Found In The Repository" when Importing Knowledge Modules in "Synonym INSERT" Mode (Doc ID 2357394.1). Last updated on ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
As mentioned the new debug output should tell you exactly which repository is hanging. I agree that a network related issue is now likely from what I know.
I will close the ticket for now but please feel free to comment with more information when available and this can be reopened.
Hello, we still couldn’t find a way narrow down the problem. We suspect it is a network problem rather than a bug.