bug: Eject/recreate silently fails if disk is locked

[zxcat]

Steps to reproduce:

1. create new TmpDisk (named test for example)
2. put some files on it
3. make it locked with some app, e.g. cd /Volumes/test in iTerm
4. Try to eject or re-create using TmpDisk menu
5. check if disk exists (if ejected) or files (from step.2) no more exist

expected: disk disappears on eject or contains no files from step2

actual: nothing happens

furthermore, it seems TmpDisk enters some buggy state. e.g. even if I unlock disk (cd ..). I can't eject or re-create it. And If I eject if using Finder, TmpDisk still shows it in the "Current TmpDisks" menu.

note: maybe it's not iTerm who locks a disk but zsh/plugins/etc, but I can repeat this behavior with other apps, which prevent disk ejection while use it.

[imothee]

Hi @zxcat - MacOS used to throw a system alert when an in use disk was attempted to be ejected (so I routed the errors to the console). I'll have to check and see when that functionality changed and if I can add some alerting to the app or if I need to version the functionality.

The original TmpDisk was built more than 10 years ago so it's very possible that MacOS hasn't done that for a long time.

[imothee]

Turns out the latest Swift libraries do not throw errors for Disk in Use.
Have added an alert + force eject functionality to https://github.com/imothee/tmpdisk/releases/tag/v2.0.6-alpha

Would love to get some eyes testing it before releasing it to the public channel.
Thanks!