From: Jeff King <peff@peff.net>
To: Luke Diamand <luke@diamand.org>
Cc: Git Users <git@vger.kernel.org>
Subject: Re: Partial clone - bad pack header?
Date: Tue, 5 Feb 2019 00:28:45 +0100 [thread overview]
Message-ID: <20190204232844.GA2366@sigill.intra.peff.net> (raw)
In-Reply-To: <CAE5ih7-Gi6i8ZRDjsVELLesTORRDxvrLYf00DYTBRFUWUmAAdw@mail.gmail.com>
On Mon, Feb 04, 2019 at 01:45:35PM +0000, Luke Diamand wrote:
> I tried to do a partial clone, but it gave me a "bad pack header". Is
> there anything I can do to debug this?
>
> I did "git config uploadpack.allowfilter true" in my repo.
> Then I went to a scratch directory and did:
> $ git clone --filter=blob:limit=10M ssh://localhost/~/git/my_big_repo
> remote: Enumerating objects: 1619425, done.
> remote: Counting objects: 100% (1619425/1619425), done.
> remote: Compressing objects: 100% (362435/362435), done.
> remote: Total 1619425 (delta 1225623), reused 1604277 (delta 1211975)
> Receiving objects: 100% (1619425/1619425), 10.34 GiB | 35.61 MiB/s, done.
> Resolving deltas: 100% (1225623/1225623), done.
> Note: checking out 'a943f529b4781f34602f1ad5aab99a8699975c29'.
> [...]
> fatal: the remote end hung up unexpectedly
> fatal: protocol error: bad pack header
> warning: Clone succeeded, but checkout failed.
Just a guess, but does setting uploadpack.allowAnySHA1InWant to "true"
in the source repo help?
By default, upload-pack will not allow the client to request those
arbitrary blob sha1s. I thought it was _supposed_ to notice this and
complain with a nice error message, but I know I have run into cases in
the past where it does not (but never tracked it down -- this may well
be one of them).
-Peff
next prev parent reply other threads:[~2019-02-04 23:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 13:45 Partial clone - bad pack header? Luke Diamand
2019-02-04 23:28 ` Jeff King [this message]
2019-02-05 10:14 ` Luke Diamand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190204232844.GA2366@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=luke@diamand.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).