[unison-users] Invalid argument: String.blit / Bytes.blit_string

[[e-mail] [unison-users]]

Hi there,


Over the years there have been a few reports of Unison failing with an "Invalid argument: String.blit / Bytes.blit_string" error, but with no real resolution found. The common factors seem to be that the error affects Mac users and can be cleared by removing the fingerprint cache files (~/.unison/fp<hash>).


I ran into the issue recently and I've just been investigating the root cause. I've added what details I have to https://github.com/bcpierce00/unison/issues/61 https://github.com/bcpierce00/unison/issues/61 but the basics are that I have a fingerprint cache file that seems to be corrupt and which causes the path decompression to fail. I can't be exactly sure what led to the file being corrupt as I have been working around the issue for a while by using a different profile to cover the same directory. I think I've reached the limit of what I can do on my own as I don't know OCaml or the internals of Unison, but I'd be happy to help if there are things I can try on my end to help someone track the issue down.


Cheers,


-Mark.

['Benjamin C. Pierce' [e-mail] [unison-users]]

Probably the easiest / cleanest solution is just to catch the exception and pretend that the fingerprint file doesn’t exist.

- B

Post by mhw+***@kremvax.net [unison-users]
Hi there,
Over the years there have been a few reports of Unison failing with an "Invalid argument: String.blit / Bytes.blit_string" error, but with no real resolution found. The common factors seem to be that the error affects Mac users and can be cleared by removing the fingerprint cache files (~/.unison/fp<hash>).
I ran into the issue recently and I've just been investigating the root cause. I've added what details I have to https://github.com/bcpierce00/unison/issues/61 <https://github.com/bcpierce00/unison/issues/61> but the basics are that I have a fingerprint cache file that seems to be corrupt and which causes the path decompression to fail. I can't be exactly sure what led to the file being corrupt as I have been working around the issue for a while by using a different profile to cover the sa! me directory. I think I've reached the limit of what I can do on my own as I don't know OCaml or the internals of Unison, but I'd be happy to help if there are things I can try on my end to help someone track the issue down.
Cheers,
-Mark.