Mike Hommey

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...

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...

Is it the same repo you fixed in #280? Can you create a git bundle the same way you did back then?

Can you do another one with `git bundle create $file refs/cinnabar/metadata refs/cinnabar/checked refs/cinnabar/broken`? (without `--not ...`)

This time, your repo is more busted than last time, but it's still the same root cause (#207). I'm bummed that the situation was not [detected](https://github.com/glandium/git-cinnabar/blob/6ee02238b841b67f63b5d4d5dbc5cf13f0de7dce/cinnabar/githg.py#L1307). You seem to have...

``` ERROR Error in file b'f917b11e765e626d9459c18cc3771e4decd75880' ERROR Error in file b'8fc2e6a72551b0e749377adf2af35cdbd14c94ff' Checking 1417 imported file root and head revisions ERROR Object of type bytes is not JSON serializable ``` Is...

> I believe I saw it at least once before this thinking I wish you had reported it back then because it showed that the diagnostic code for #207 worked...

> TIL it exists, but I think I never fetch from try. Something doesn't line up. When you push to try, can you check whether `git rev-parse refs/cinnabar/metadata` returns the...

did you `git cinnabar rollback b1fe9b8493dbb38038c230f2fb346bfa803a60fe` as per https://github.com/glandium/git-cinnabar/issues/295#issuecomment-1026529368 ?

Kind of. I'm baffled you didn't see the other error message before that...