From: Junio C Hamano <junkio@cox.net>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: merlyn@stonehenge.com (Randal L. Schwartz)
Cc: git@vger.kernel.org
Subject: Re: maybe breakage with latest git-pull and http protocol
Date: Sat, 15 Oct 2005 09:04:10 -0700 [thread overview]
Message-ID: <7vd5m6py11.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <863bn3lypn.fsf@blue.stonehenge.com> (Randal L. Schwartz's message of "15 Oct 2005 06:03:00 -0700")
merlyn@stonehenge.com (Randal L. Schwartz) writes:
> OK, it happened this morning. While syncing to update from
> yesterday's version, I got:
Thanks.
> localhost:~/MIRROR/git-GIT % git-pull
> Fetching refs/heads/master from http://www.kernel.org/pub/scm/git/git.git using http
> Getting alternates list
> got 4546738b58a0134eef154231b07d60fc174d56e3
> walk 4546738b58a0134eef154231b07d60fc174d56e3
> got d402d5566fdf226697a386dfb9858e5d954e9b91
> got 873d8e5652c06c3891278f33546c437efc209c2d
> walk d402d5566fdf226697a386dfb9858e5d954e9b91
> error:
> Getting pack list
> got 0207ab18a3876249a928e7539d8f594a4f6921f1
Here is the beginning of a session that succeeded:
: siamese; GIT_DIR=. git-http-fetch -v -a heads/master \
http://www.kernel.org/pub/scm/git/git.git/
Getting alternates list
got 4546738b58a0134eef154231b07d60fc174d56e3
walk 4546738b58a0134eef154231b07d60fc174d56e3
got d402d5566fdf226697a386dfb9858e5d954e9b91
got 873d8e5652c06c3891278f33546c437efc209c2d
got 5ad4a2766d34569f3a1278544ab64978fab14cc8
walk d402d5566fdf226697a386dfb9858e5d954e9b91
...
The difference is that this log gets 5ad4a2 blob, before it
starts walking d402d5 commit, while Merlyn's log shows we tried
to walk that commit before getting the blob. I think what is
happening is:
- we request 454673 commit, and get it.
- we start requesting trees, blobs, and parent commit
reachable from it. Especially, 5ad4a2 blob and d402d5
commit are asked.
- as soon as d402d5 commit arrives we walk and find out we
need 5ad4a2 blob. In the case that happened to work, that
blob has already arrived because it was also part of the
454673 commit, but in Merlyn's case that blob has not
arrived yet. "Getting pack list" on the next line is an
indication that the fetch_object incorrectly decided that
the object we are waiting for is not available unpacked,
which does not (and should not) happen in the case we got
the blob object in time.
I have a suspicion that the recent multi-fetch work has some
interesting interaction with the assumption Sergey's fetch.c
optimization makes.
next prev parent reply other threads:[~2005-10-15 16:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-13 0:53 maybe breakage with latest git-pull and http protocol Randal L. Schwartz
2005-10-13 5:50 ` Junio C Hamano
2005-10-14 10:58 ` Randal L. Schwartz
2005-10-14 15:42 ` Junio C Hamano
2005-10-14 16:18 ` Randal L. Schwartz
2005-10-14 19:56 ` Daniel Barkalow
2005-10-15 13:03 ` Randal L. Schwartz
2005-10-15 16:04 ` Junio C Hamano [this message]
2005-10-15 16:22 ` Junio C Hamano
2005-10-15 19:41 ` Daniel Barkalow
2005-10-15 21:56 ` Nick Hengeveld
2005-10-15 21:21 ` Nick Hengeveld
2005-10-15 16:37 ` Junio C Hamano
2005-10-15 17:13 ` Junio C Hamano
2005-10-15 21:57 ` Nick Hengeveld
2005-10-15 22:04 ` Randal L. Schwartz
2005-10-20 17:43 ` Nick Hengeveld
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=7vd5m6py11.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=barkalow@iabervon.org \
--cc=merlyn@stonehenge.com \
/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).