Re: could not freshen shared index ..../sharedindex.0000000000000000000000000000000000000000'
- Date: Sat, 9 Feb 2019 12:00:59 +0700
- From: Duy Nguyen <pclouds@xxxxxxxxx>
- Subject: Re: could not freshen shared index ..../sharedindex.0000000000000000000000000000000000000000'
On Fri, Feb 8, 2019 at 11:39 PM Luke Diamand <luke@xxxxxxxxxxx> wrote:
> On Fri, 8 Feb 2019 at 10:02, Duy Nguyen <pclouds@xxxxxxxxx> wrote:
> > On Wed, Feb 06, 2019 at 10:25:25AM +0000, Luke Diamand wrote:
> > > I've recently started seeing a lot of this message when doing a rebase:
> > >
> > > warning: could not freshen shared index
> > > '/home/ldiamand/git/dev_full/.git/worktrees/gcc8-take-2/sharedindex.0000000000000000000000000000000000000000'
> > There are only two places in the code that could print this. The one
> > in read_index_from() can't happen unless is_null_oid() is broken (very
> > very unlikely).
> > The other one is in write_locked_index() which could happen in theory
> > but I don't understand how it got there. If you could build git, could
> > you try this patch and see if it helps?
> They've gone away!
Great! Since you seem able to reproduce this (and can build git!)
could you try bisect to pin point the commit that causes this problem?
That would help a lot. I think you could start maybe from v2.19.0