-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"fatal: Malformed file chunk for " error on git fetch #207
Comments
I've tried to create a clone of mozilla-unified on my mac with the same |
Thanks again for the archive of your As mentioned on irc, https://hg.mozilla.org/mozilla-unified/rev/be98a5ed931b is when your clone ended up definitely broken, and I was able to reproduce using the state of your clone before that, but it turned out the underpinning of the breakage appeared a few days earlier, when pulling https://hg.mozilla.org/mozilla-unified/rev/1692e4521fb0 and https://hg.mozilla.org/mozilla-unified/rev/f94486bc39182d98646991f8. What happened is that some files were renamed, and the mercurial metadata of those renames were not stored during the pull. Incidentally, another file rename occurred just shortly before that, and was recorded properly. It was on pulling https://hg.mozilla.org/mozilla-unified/rev/9deb23f8b29b. Considering the contents of your clone back then, I know with certainty that you were using at least git-cinnabar commit 514b404, but that one works for me. As mentioned on irc, it would be useful to figure out what version of git-cinnabar you were using back then, and with chance, it's available in the reflog in your git-cinnabar clone. Can you check the output from |
For reference:
|
I tried all combinations of git-cinnabar and helper versions possible in the range where your repository works (that's about 10k combinations), with a pull of the same heads that made your clone break, and none of them reproduced the issue. :( |
The root cause has still not been identified. #214 is another occurrence of the same problem, and I wasn't able to reproduce it with the exact version of git-cinnabar and the helper that were used there. My plan of action at this point is, essentially:
|
The nag was added to detect #207, but we're now trying to detect it on any repo update.
I've been getting an error when fetching unified with git cinnabar since yesterday afternoon (I've never seen this problem before fetching multiple times a day). This is what my output looks like:
This is my git config:
Any help would be highly appreciated. Thanks!
The text was updated successfully, but these errors were encountered: