<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><div></div><div><br class=""></div><div><br class=""><blockquote type="cite" class=""><div class="">On Dec 12, 2017, at 5:20 PM, Benjamin C. Pierce <<a href="mailto:bcpierce@cis.upenn.edu" class="">bcpierce@cis.upenn.edu</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">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...<div class=""><ul class="MailOutline"><li class="">Does anybody know anything about recent changes in the way resource forks work in OSX?</li><li class="">Has anybody else who has had their hands in this part of the code upgraded to High Sierra yet?</li></ul><div class="">Thanks!</div></div><div class=""><br class=""></div><div class=""> - Benjamin</div><div class=""><br class=""></div><div class="">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.</div><div class=""><br class=""></div></div></div></blockquote></div><br class=""></div></div></div></body></html>