{"thread":{"id":"34881","subject":"[BUG] rebase not recovering gracefully from repack error","startedAt":"2013-09-08T20:46:43Z","lastAt":"2013-09-08T20:46:43Z","messageCount":1,"participants":["Yann Dirson"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"227148","messageId":"20130908204643.GD8767@home.lan","threadId":"34881","inReplyTo":null,"subject":"[BUG] rebase not recovering gracefully from repack error","fromName":"Yann Dirson","fromEmail":"ydirson@free.fr","sentAt":"2013-09-08T20:46:43Z","receivedAt":"2013-09-08T20:46:43Z","isPatch":false,"sender":{"key":"ydirson@free.fr","avatar":null},"body":"(patches|REBASE 8/9)$ git rebase --continue\nApplying: Check for __unix__ instead of __linux\nApplying: Completely disable crash handler on archs other than i386 and amd64\nAuto packing the repository for optimum performance. You may also\nrun \"git gc\" manually. See \"git help gc\" for more information.\nerror: Could not read a7d470051f53f4e4c9247df752583868a79ec70b\nfatal: Failed to traverse parents of commit e6d2f264969207e337953717c260d37daa0a8554\nerror: failed to run repack\n(patches|REBASE 10/9)$ cat .git/rebase-apply/next \n10\n(patches|REBASE 10/9)$ \n\n\nThe last patch has been dealt with and I consider the rebase done.\nRebase would be bombing out without cleaning behind it when the auto\nrepack fails ?\n\n\nOn another aspect, I find the repack error is suspect: \"git fsck\n--no-dangling\" has nothing to complain about, and the missing commit\nis the real ancestor of a grafted commit.  I suppose it has been gc'd\nby a buggy git version, as I recall seeing such a fix on the list some\ntime ago.  (yes, I shouldn't be using grafts any more, but that\nparticular one dates back to 2006 ;)\n\n-- \nYann\n\n[v1.8.4]\n"}]}