Closed nomennescio closed 4 months ago
Any chance there's a .git/fast_import_crash_<number>
file after the bad run (where <number>
is some random positive integer, like 8434)? If yes, can you share its contents?
I already threw away the directory, but I will try to reproduce, however, that will take a while. I noticed however that switching to a different platform, doing a fast export|fast import
, then switching back and run filter-repo
did work, so that's my current work-around. (I could reproduce the issue)
Might it be there is an issue with atypical replacement objects?
I think it'd be less likely to be an atypical replacement object, and more likely to be some non-canonical object (a tree with multiple of the same-named path? extended headers of some kind? who knows?) that doesn't parse nicely in filter-repo (though which filter-repo parses just well enough to not die itself but pass along something to fast-import which fast-import doesn't understand), and yet which when simply trying to canonicalize via the fast-export | fast-import round-trip gets stripped out or cleaned up.
But, without more information from the repo, particularly the output from the .git/fast_import_crash_<number>
file, it's hard to dig any further.
For now, I'm going to assume you've moved on and just close the ticket out. But, if you still have access to this repo and can reproduce, please do feel free to retrigger, provide the fast import crash file and reopen this ticket.
Although I was able to convert a repo, after some
git replace
s, I get errors trying to redo it. First did an analysis to check if I could learn more:Then tried running again
can't get anything more out of it, repeating leads to the same error. How to solve this?