* Partial clone - bad pack header?
@ 2019-02-04 13:45 Luke Diamand
2019-02-04 23:28 ` Jeff King
0 siblings, 1 reply; 3+ messages in thread
From: Luke Diamand @ 2019-02-04 13:45 UTC (permalink / raw)
To: Git Users
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'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
git checkout -b <new-branch-name>
fatal: the remote end hung up unexpectedly
fatal: protocol error: bad pack header
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry the checkout with 'git checkout -f HEAD'
$ git checkout origin/master
fatal: the remote end hung up unexpectedly
fatal: protocol error: bad pack header
$ git --version
git version 2.20.1.611.gfbb209baf1
There's plenty of disk space left.
Thanks,
Luke
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Partial clone - bad pack header?
2019-02-04 13:45 Partial clone - bad pack header? Luke Diamand
@ 2019-02-04 23:28 ` Jeff King
2019-02-05 10:14 ` Luke Diamand
0 siblings, 1 reply; 3+ messages in thread
From: Jeff King @ 2019-02-04 23:28 UTC (permalink / raw)
To: Luke Diamand; +Cc: Git Users
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Partial clone - bad pack header?
2019-02-04 23:28 ` Jeff King
@ 2019-02-05 10:14 ` Luke Diamand
0 siblings, 0 replies; 3+ messages in thread
From: Luke Diamand @ 2019-02-05 10:14 UTC (permalink / raw)
To: Jeff King; +Cc: Git Users
On Mon, 4 Feb 2019 at 23:28, Jeff King <peff@peff.net> wrote:
>
> 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?
That's a very good guess - it works a treat with that!
>
> 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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2019-02-05 10:14 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-02-04 13:45 Partial clone - bad pack header? Luke Diamand
2019-02-04 23:28 ` Jeff King
2019-02-05 10:14 ` Luke Diamand
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).