CopyFileFromUSB does not fail when the user has removed the stick. Instead it sends the successEvent. To duplicate, insert stick, press MountUSB, remove the stick, press CopyFromUSB.

Admittedly, one should not remove the stick until it has been unmounted BUT a user will do this inadvertently and my program needs to handle it gracefully.

Note that CopyToUSB does fail and thus passes this test.

CopyFileFromUSB when user has removed stick
Note that the fail event is never sent even though the copy fails.
ENTER Script CopyFileFromUSB
EXIT Script CopyFileFromUSB
cp: Can't open source file. (/mnt/stick/filename)
ENTER Script CopyFileFromUSBComplete ( CopyFileFromUSBFail should have been sent )
NM-server: pulse received
code = 0xffffffdd
coid = 0xffffffff
NM-server: pulse received
code = 0xffffffdf
coid = 0x40000021
EXIT Script CopyFileFromUSBComplete

dberezowski,

I am working your bug and I am trying to best characterize it incorporating dwills comments over on the ScriptFileAccessDemo script errors thread.

I'll update you when I have more information to share.

Thanks for the find!

dberezowski,

We incorporated this in our latest development build. I tested it this afternoon and showed that we now do send the fail and succeed events correctly. Look for this in the coming 2.3 release.

Thanks for the find.

And thank you for the excellent support!