• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: FSCopyObjectAsync still buggy and useless after all these years
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: FSCopyObjectAsync still buggy and useless after all these years


  • Subject: Re: FSCopyObjectAsync still buggy and useless after all these years
  • From: Steve Gehrman <email@hidden>
  • Date: Sun, 26 Sep 2010 21:25:12 -0700


Who's the guy responsible for this API?  I've been reporting data destroying bugs since 10.4 and they completely refuse to fix it.

Here's another bug.  Use FSMoveObjectAsync to move a folder across volumes.  Move to a folder to a network volume is easiest to duplicate.  When it's copying, unplug the network cable and the API will happily delete the source folder destroying data.  Why is this acceptable for this many years?

-steve

On Sep 24, 2010, at 8:23 AM, Martin Halter wrote:

Dear James

no you're not the only ones. Raskin also uses FSCopyObjectAsync to copy files and i grew some grey hair implementing it. We also opened a radar on the overwrite issue and it was marked as duplicate on 06-Aug-2010. 

To state it here again: FSMoveObjectAsync and FSCopyObjectAsync replace Items at the destination with the same name using kFSFileOperationDefaultOptions. 

The best thing to have would be NSURLDownload also working for directories, as it works for single file-URLs. Or any other mean of copying files asynchronously with the possibility to get notified about progress. 

mahal

Raskin ______ Beyond Desktop

Raskin Software LLC
Walchestrasse 30
8006 Zurich, Switzerland
Phone +41 44 450 6975

raskinformac.com

Am 23. Sep 2010 um 20:03 schrieb James Bucanek <email@hidden>:

Eric Schlegel <mailto:email@hidden> wrote (Tuesday,
September 21, 2010 11:42 PM -0700):

>Steve, although I don't work on FSCopyObjectAsync, perhaps we could make
>progress if you posted the Radar numbers of the bugs you've filed about these
>issues, so we can see what information has been determined internally.

If we're sharing open bugs against FSCopyObject*, here are my
two pet bugs:

7102368 - FSCopyObjectSync ignores kFSFileOperationOverwrite

7185117 - FSCopyObjectSync returns invalid target FSRef on
an Airport Extreme volume

These were actually introduced in 10.6. I've written workarounds
for both, but I'm surprised they weren't caught before the 10.6
release or been addressed since. I can only imagine these bugs
would mess up a lot of software ... unless Steve and I are the
only ones using this API. :)

James
--
James Bucanek

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Filesystem-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:


Do not post admin requests to the list. They will be ignored. Filesystem-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >Re: FSCopyObjectAsync still buggy and useless after all these years (From: Martin Halter <email@hidden>)

  • Prev by Date: Re: wrong atime created by NFS clients (Mac OX 10.5 and 10.6).
  • Next by Date: FSGetCatalogInfo returns zero permissions for /Volumes/VolumeName directory
  • Previous by thread: Re: FSCopyObjectAsync still buggy and useless after all these years
  • Next by thread: wrong atime created by NFS clients (Mac OX 10.5 and 10.6).
  • Index(es):
    • Date
    • Thread