From: Junio C Hamano <junkio@cox.net>
To: merlyn@stonehenge.com (Randal L. Schwartz)
Cc: Daniel Barkalow <barkalow@iabervon.org>, git@vger.kernel.org
Subject: Re: maybe breakage with latest git-pull and http protocol
Date: Sat, 15 Oct 2005 10:13:08 -0700 [thread overview]
Message-ID: <7v1x2mog9n.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:
>>>>>> "Daniel" == Daniel Barkalow <barkalow@iabervon.org> writes:
>
> Daniel> Can you give a general description of what happens? I've
> Daniel> noticed that I sometimes get spurious error messages that
> Daniel> don't actually affect the download, which I haven't tracked
> Daniel> down yet.
>
> OK, it happened this morning. While syncing to update from
> yesterday's version, I got:
>
> 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
Sorry for an empty message.
Could you do the following to establish a reliable way to
reproduce this problem in your setup, so we can diagnose it
better?
First please apply this patch to http-fetch.c and rebuild your
git.
diff --git a/http-fetch.c b/http-fetch.c
index 784aedf..2c1f72c 100644
--- a/http-fetch.c
+++ b/http-fetch.c
@@ -1009,7 +1009,10 @@ static int fetch_object(struct alt_base
}
if (request->curl_result != CURLE_OK && request->http_code != 416) {
- ret = error("%s", request->errorstr);
+ ret = error("%s (curl_result = %d, http_code = %ld, sha1 = %s)",
+ request->errorstr, request->curl_result,
+ request->http_code,
+ sha1_to_hex(request->sha1));
release_request(request);
return ret;
}
Then, using that:
$ cd ~/MIRROR
$ rm -fr git-BROKEN
$ git-clone -n http://www.kernel.org/pub/scm/git/git.git git-BROKEN
If you got any error here, then we know we already have a way
to reproduce. Please give us a log.
If the above succeeds, then please run
$ git-fsck-objects --full
to make sure we got things OK. This should not report
anything.
Now, I'd like to make this repository as close as I can make it
to "after yesterday's pull", by rewining its top commit back to
this one:
commit f7aac2eac96b637755c89c2405a41749c8f6033a
Author: Linus Torvalds <torvalds@osdl.org>
Date: Thu Oct 13 15:38:29 2005 -0700
Add "-l" flag for repacking only local packs
$ git-reset --hard f7aac2eac96b637755c89c2405a41749c8f6033a
$ git-update-ref refs/heads/origin f7aac2eac96b637755c89c2405a41749c8f6033a
Since proposed updates (pu) branch usually contains everything
that is in the master, we need to get rid of it for this
experiment:
$ rm -f .git/refs/heads/pu
and the we get rid of objects that were added since then:
$ git-prune
$ git-fsck-objects --full
Now we are hopefully as close as "after yesterday's pull" state.
$ git-http-fetch -a -v heads/master http://www.kernel.org/pub/scm/git/git.git/
This will start with something like:
Getting alternates list
got 4546738b58a0134eef154231b07d60fc174d56e3
walk 4546738b58a0134eef154231b07d60fc174d56e3
got d402d5566fdf226697a386dfb9858e5d954e9b91
got 873d8e5652c06c3891278f33546c437efc209c2d
walk d402d5566fdf226697a386dfb9858e5d954e9b91
...
if you see the same error, instead of the empty "error:" up
above, we may see a bit more information.
next prev parent reply other threads:[~2005-10-15 17:13 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
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 [this message]
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=7v1x2mog9n.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.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).