-
-
Notifications
You must be signed in to change notification settings - Fork 933
kill_after_timeout doesn't seem to affect clone_from function #1215
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
Comments
Could you provide an example that is reproducible by executing a python script?
|
This is what I am basically trying to do the issue mentioned here. I am cloning multiple repos running in a multiprocessing environment, after cloning some of the repos, the git process seems to hang on some causing the entire script to slow down ultimately hanging the whole script. Upon looking at the debug errors, it looks it's stuck in a clone_from call. So what I had to do was to kill the process after a 10 second timeout, but it wouldn't happen either. |
Thanks a lot for the additional description. However, it's not what could move this issue forward as there is no way to reproduce it. Thus I am closing it but will be happy to reopen once a script was provided. |
Hey, import git
git.Repo.clone_from(
"https://github.com/trustwallet/assets",
"/tmp/output",
depth=1,
kill_after_timeout=0.1 # <--- This will never bail
) |
Thanks for the script, appreciated. For completeness, which OS/platform are you testing on and which GitPython version are you using (along with the python interpreter version)? Thanks again. |
Running in a Linux container |
@Byron I may have some time to look into soon :) |
It seems that because |
As mentioned in the title, it just doesn't seem to work. I've tried passing as_process=False as mentioned in another issue, but that ends up in duplicate keyword args exception.
repo = git.Repo.clone_from(url, repo_folder_name, progress=None, quiet=True, filter="tree:0", no_checkout=True, depth=20, config="core.gitproxy=/home/git/git-proxy", kill_after_timeout=10)
The text was updated successfully, but these errors were encountered: