[Unison-hackers] High Sierra / resource forks

[Benjamin C. Pierce]

We were warned a couple months ago that at least one person was having trouble with strange transfer failures on OSX 10.13 (High Sierra).  I did some digging today and was able to track it down to a fingerprint mismatch on the transferred resource fork (which looked like a failure in the “rename” operation, because of some silliness).  Specifically, it appears that the received file has an empty resource fork, although the original had a non-empty one.  That’s as far as I got, and I need to switch to other things now, but I wonder...
Does anybody know anything about recent changes in the way resource forks work in OSX?
Has anybody else who has had their hands in this part of the code upgraded to High Sierra yet?
Thanks!

   - Benjamin

P.S.  I created a HighSierraDebugging branch to play with.  Most of the changes are extra debugging statements, but I also masked the wrong failure message.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://LISTS.SEAS.UPENN.EDU/pipermail/unison-hackers/attachments/20171212/97517cdd/attachment.html>