git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: could not freshen shared index ..../sharedindex.0000000000000000000000000000000000000000'

From
Duy Nguyen <pclouds@gmail.com>
Date
Feb 8, 2019, 10:02 UTC
Message-ID
<20190208100221.GA22283@ash>
In-Reply-To
<CAE5ih79DuU5Wrk4p+wpQX3j6bgyA2_ZgXYJX-tGvZpYhWazWqA@mail.gmail.com>
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?

-- 8< --
diff --git a/read-cache.c b/read-cache.c
index f68b367613..5ad71478dc 100644
--- a/read-cache.c
+++ b/read-cache.c
@@ -3165,6 +3165,7 @@ int write_locked_index(struct index_state *istate, struct lock_file *lock,
 		fill_fsmonitor_bitmap(istate);
 
 	if (!si || alternate_index_output ||
+	    (si && is_null_oid(&si->base_oid)) ||
 	    (istate->cache_changed & ~EXTMASK)) {
 		if (si)
 			oidclr(&si->base_oid);
-- 8< --


> (There's a repo called dev_full, and I've got a worktree where I'm
> working on my 3rd attempt to make it work with gcc8).
> 
> That file doesn't actually exist but there are a bunch of
> sharedindex.XXX files in there with more convincing looking names.
> 
> 2.20.1.611.gfbb209baf1
--
Duy
Previous: Christian CouderNext: Luke Diamand
Message 3 of 16 in “could not freshen shared index ..../sharedindex.0000000000000000000000000000000000000000'”
  1. Luke DiamandFeb 6, 2019
  2. Christian CouderFeb 6, 2019
  3. Duy NguyenFeb 8, 2019
  4. Luke DiamandFeb 8, 2019
  5. Duy NguyenFeb 9, 2019
  6. Luke DiamandFeb 9, 2019
  7. Duy NguyenFeb 9, 2019
  8. unpack-trees.c: fix writing "link" index ext with null base oidNguyễn Thái Ngọc Duy, Feb 9, 2019
  9. Luke DiamandFeb 9, 2019
  10. Elijah NewrenFeb 12, 2019
  11. Junio C HamanoFeb 12, 2019
  12. Ævar Arnfjörð BjarmasonFeb 12, 2019
  13. read-cache.c: fix writing "link" index ext with null base oidNguyễn Thái Ngọc Duy, Feb 13, 2019
  14. Ævar Arnfjörð BjarmasonFeb 13, 2019
  15. Junio C HamanoFeb 8, 2019
  16. Duy NguyenFeb 9, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.