From: Nick Hengeveld <nickh@reactrix.com>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: git@vger.kernel.org
Subject: Re: Errors from http-fetch
Date: Wed, 19 Oct 2005 15:37:08 -0700 [thread overview]
Message-ID: <20051019223708.GC6160@reactrix.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0510191755280.25300@iabervon.org>
On Wed, Oct 19, 2005 at 06:10:52PM -0400, Daniel Barkalow wrote:
> I'm getting 404 for the object, which it reports. This was pulling from
> kernel.org.
Something similar was reported yesterday, and when I investigated I
found that one of the kernel.org servers was returning a 404 for the
object in question and the other wasn't. Vger bounced my reply because
it contained Content-type: headers...
> That is, it was a later object that prompted getting the pack, because
> either the server decided to send that error message sooner, some packet
> got dropped and retransmitted, the connection got a lower-numbered file
> descriptor and they were ready at the same time, or something like that.
I could see that happen if the pack appeared on the repo after #1 404ed
and subsequently decided there were no packs, and before #2 404ed. Or,
as was the case I saw yesterday, servers with the same DNS name aren't
in sync. However, the pack download for #2 should never start in that
case because fetch() for #1 would fail and exit.
> Another thing I noticed was that it was in the middle of downloading the
> pack when it suddenly exitted due to not being able to find the object; it
> would probably be worth having a call to finish up the active transfers
> after giving up on completing the whole thing, since we probably do
> actually want to finish downloading a big pack if we've started.
I'm not sure how that could happen - once a pack download request
starts, it has to finish before any fetch() calls can fail. However,
there could certainly be other object requests in process when one
fails, and it would be polite to let them finish.
--
For a successful technology, reality must take precedence over public
relations, for nature cannot be fooled.
next prev parent reply other threads:[~2005-10-19 22:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-19 19:46 Errors from http-fetch Daniel Barkalow
2005-10-19 21:26 ` Nick Hengeveld
2005-10-19 22:10 ` Daniel Barkalow
2005-10-19 22:37 ` Nick Hengeveld [this message]
2005-10-20 20:02 ` Daniel Barkalow
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=20051019223708.GC6160@reactrix.com \
--to=nickh@reactrix.com \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.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).