Re: False positives in git diff-index

[Jakub Narebski <jnareb@gmail.com>]

Alexander Gladysh <agladysh@gmail.com> writes:

> On Tue, Jan 4, 2011 at 14:47, Zenaan Harkness <zen@freedbms.net> wrote:
> > On Tue, Jan 4, 2011 at 20:45, Alexander Gladysh <agladysh@gmail.com> wrote:

> > > Nobody is interested?
> 
> > Your problem set appears that you have a rather gnarly corner case
> > issue, arising from your custom build processes. Although git really
> > is amazing, I believe you may well be pushing git to its technological
> > limits.
> 
> Committing few megabytes of data several times per second is
> technological limits? I do not believe so.

Well, at least it is not what version control system is about; git is
designed towards manual and not automatic commits, and version control
of source code.

> > So your problem could be quite hard to debug, whilst being distinctly
> > difficult to ascertain the root causes.

> 1. I found a reproducible case for a hard to catch bug in Git. (This
> is a bug in Git, not in my build process.) This bug in its
> intermittent form annoyed me for quite some time — several months at
> least — and is likely to annoy other users. (I'm not *that* unique!)

But it is reproductible to you: from what I understand you didn't find
some minimal example to reproduce this issue without need for access
your proprietary build process.

AG> Unfortunately I can not share it or create a minimal example ? the
AG> case is triggered by a custom complicated automated build process on a
AG> private repository.

> 3. I'm willing to help Git developers with catching this bug for
> mutual benefit — I will get rid of annoying issue and make my
> deployment code more robust. Git will, well, be a bit more robust as
> well.

To debug it, if you cannot do it yourself, you would have to find git
developer who is both knowledgeable about fairly deep part of git
code, and can work with remote debugging with you at remote.


P.S. Somewhere in the depths of git maling list archive (it didn't
unfortunately made it to "Interfaces, Frontends and tools" page on git
wiki) there is tool/script for anonymizing git repository, to allow
debugging of bugs which occurs in some repositories that cannot be
made public.  Perhaps something similar could be done for your build
process (you need to reproduce only stat + git part)?

-- 
Jakub Narebski
Poland
ShadeHawk on #git