-
Notifications
You must be signed in to change notification settings - Fork 62
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
Incremental clone progress in case of transient network failure? #317
Comments
Perhaps there's something else going on here too -- twice in a row (once with Is there a way to dump exactly the request that failed so I can match it up to logs on the server side? |
You can set |
As for the original question, it's unfortunately not possible. What happens is that git asks git-cinnabar to grab a bunch of refs corresponding to the repo tips, and git-cinnabar has to create those refs. If it doesn't, git will make the clone will fail (which is what happens in your case). What you can do, however, is clone the bundle and update with the real repo.
I guess there could be a |
With this patch the clone can go a little further but now fails with an HTTP error 503 on the getbundle command.
|
Mercurial hits the same kind of problem if you use a version older than 3.8, or if you patch a current version to not support the httppostargs capability. So essentially, git-cinnabar is lacking support for arguments in HTTP POST requests. |
I need to do more testing, but I have a proof-of-concept implementation of HTTP POST requests on the I also haven't decided yet whether I'll land this in a 0.6.x release ( |
I tried interrupting it partway through, during |
On the That said, the issue here about incremental progress for clone (or fetch or unbundle) remains -- it looks like there's no amount of partial progress that can be saved in the event of interruption in any of these paths? |
I assume that I can't just do something like
and then run
git fetch --depth=N
in a loop with increasing N, because git-cinnabar has to start from the root of the DAG to create git hashes all the way to the leaves.Is there a way to make git-cinnabar save its incremental progress in the event of a transient network failure so it can pick up where it left off?
The text was updated successfully, but these errors were encountered: