git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Daniel Barkalow <barkalow@iabervon.org>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	git@vger.kernel.org
Subject: Re: fact-import: failed to apply delta
Date: Tue, 10 Feb 2009 14:30:00 -0800	[thread overview]
Message-ID: <7vprhqkjrr.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20090210213612.GW30949@spearce.org> (Shawn O. Pearce's message of "Tue, 10 Feb 2009 13:36:12 -0800")

"Shawn O. Pearce" <spearce@spearce.org> writes:

> Daniel Barkalow <barkalow@iabervon.org> wrote:
>> On Tue, 10 Feb 2009, Shawn O. Pearce wrote:
>> > 
>> > We should dump the cached_objects table in sha1_file.c during
>> > a checkpoint in fast-import.
>> 
>> No, that one's keyed by sha1, and doesn't get collisions; it's the 
>> delta_base_cache that's the issue; it's keyed by struct packed_git * and 
>> offset.
>
> Uh, yea, I realize that after I sent the message.  Does this patch
> fix it for you?
>
> --8<--
> Clear the delta base cache during fast-import checkpoint
>
> Otherwise we may reuse the same memory address for a totally
> different "struct packed_git", and a previously cached object from
> the prior occupant might be returned when trying to unpack an object
> from the new pack.

Can this be made more automatic?

For example if you do this every time a new pack is installed to
sha1_file(), like in add_packed_git() perhaps, wouldn't that be much less
error prone?

  parent reply	other threads:[~2009-02-10 22:31 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-10  3:26 fact-import: failed to apply delta Daniel Barkalow
2009-02-10 10:28 ` Johannes Schindelin
2009-02-10 15:56   ` Shawn O. Pearce
2009-02-10 17:15     ` Daniel Barkalow
2009-02-10 17:22       ` Shawn O. Pearce
2009-02-10 17:47         ` Daniel Barkalow
2009-02-10 19:12           ` Shawn O. Pearce
2009-02-10 20:03             ` Daniel Barkalow
2009-02-10 20:12               ` Shawn O. Pearce
2009-02-10 21:19                 ` Daniel Barkalow
2009-02-10 21:25                   ` Shawn O. Pearce
2009-02-10 21:32                     ` Daniel Barkalow
2009-02-10 21:36                       ` Shawn O. Pearce
2009-02-10 21:51                         ` Daniel Barkalow
2009-02-10 22:30                         ` Junio C Hamano [this message]
2009-02-10 22:47                           ` Junio C Hamano
2009-02-10 23:09                             ` Shawn O. Pearce
2009-02-10 23:15                               ` Junio C Hamano
2009-02-10 23:16                                 ` Shawn O. Pearce
2009-02-10 23:32                                   ` Junio C Hamano
2009-02-11 18:09                             ` Daniel Barkalow
2009-02-11 18:15                               ` Shawn O. Pearce
2009-02-11 18:30                                 ` Junio C Hamano
2009-02-11 18:33                                 ` 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=7vprhqkjrr.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=barkalow@iabervon.org \
    --cc=git@vger.kernel.org \
    --cc=spearce@spearce.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).