Re: [Radmind-users] [Ext] Re: My mind is blown

[James R. <rey...@bi...>]

That’s great!

I’d like to add that if any of you have patches or any change to the source at all, if you’re too busy to format it for an official pull request, just email me the source code and I’ll try to format it nicely and get it incorporated and everything. BBEdit’s diff’ing abilities will allow me to find what you’ve changed so I’ll be able to figure it out (assuming the original wasn’t something super old like radmind 0.7).

James

On 2/9/22, 10:48 AM, "Troy V. Barkmeier via Radmind-users" <rad...@li...> wrote:
WARNING: Stop. Think. Read. This is an external email.



I honestly don't plan on figuring out the APFS issue. I think someone else has already solved it. I'm willing to test it and merge it, if it isn't already merged (I have to look).


Yep, I found and fixed this in July of 2019 when we moved to APFS with 10.14 in our labs. My original pull request is here: https://github.com/Radmind/radmind/pull/331

Looks like someone else expanded on it by adding an error check on the resource fork creation step, which is of course the right thing to do. For what it's worth, though, we've been running (and centrally logging) lapply patched with my original code from this pull hundreds of times a day across campus for nearly three years now and have yet to see lapply fail to create a file with a resource fork. :)

Best,
TVB