
this is a known issue, and happens because Unison wasn't compiledĪgainst the same OCaml versions. Note especially on the page in the last link:

It's hard to give you a precise link, as some of Google's most promising results return an empty page, but I hope these will do: Not only do the major versions of two Unison processes involved in a synchronization need to match (as you probably know), there was also an internal change in the OCaml libraries somewhere between OCaml versions 4.01 and 4.02, related to the marshaling of data. The error message "input_value: bad bigarray kind" indicates you're hitting a somewhat well-known bug in Unison.

I read several articles and most of them come to the conclusion that this is an OCaml incompatibility problem.ĭid someone else experience that error as well?

Unfortunately Unison chrashes with the following error message: Uncaught exception Failure("input_value: bad bigarray kind") I also downloaded the proposed versions of OpenSSH & Unison from and created the sync.bat as described.
Unison fsmonitor windows#
I am using the Mgt Development Environment (mgtcommerce/mgt-development-environment-5.6) on Windows 8.1.
