On Friday, September 16, 2022 at 12:35:24 AM UTC+2 Paul wrote: > However, when I upgrade to git 2.37.2, or 2.37.3, git gc suddenly starts > to fail: > fatal: unable to read 1d0f34d1c4314efcff527847755e4ccc77d44fb6 > > fatal: failed to run repack > How can I work out what reference is causing this hash to be referenced? I > would most likely be perfectly happy to drop whatever reference it is, if I > could just move to a newer version of git, and continue using git gc. >
Hi Paul I have the same issue - did you figure this out yet? I suspect that this issue comes from the following commit: https://github.com/git/git/commit/5a5ea141e7 ("revision: mark blobs needed for resolve-undo as reachable", 2022-06-09) For me, a similar error message also appears when I simply run `git rev-list --objects --indexed-objects`. Commit 5a5ea141e7 added a function add_resolve_undo_to_pending(), which calls lookup_blob() and checks if that returns NULL. However as far as I can tell, lookup_blob() almost never returns NULL - it especially doesn't return NULL for arbitrary non-existent object ids. This is as far as I've gotten in my debugging of this error so far - I thought I'd share it here. Kind regards Mathias Rav -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/9bfb2684-2e07-4ade-92bb-21853ab361bfn%40googlegroups.com.
