I've noticed that, when working with an actual device, it is possible to get into a situation where you have a stale WebDAV mount that Ambly can't cope with.
This manifests itself like the following:
java.io.IOException: Unable to create WebDAV mount point /Volumes/Ambly-303F68E9
at ambly.core$mount_webdav.invoke(core.clj:382)
at ambly.core$setup.invoke(core.clj:419)
at ambly.core.JscEnv._setup(core.clj:531)
at cljs.repl$repl_STAR_$fn__4217.invoke(repl.cljc:782)
$ ls /Volumes/Ambly-303F68E9
ls: /Volumes/Ambly-303F68E9: Operation timed out
I've found that this can be rectified by doing an umount -f but, even though Ambly has code to do this, it won't because (.exists (clojure.java.io/file "/Volumes/Ambly-303F68E9")) returns false.
I've noticed that, when working with an actual device, it is possible to get into a situation where you have a stale WebDAV mount that Ambly can't cope with.
This manifests itself like the following:
I've found that this can be rectified by doing an
umount -fbut, even though Ambly has code to do this, it won't because(.exists (clojure.java.io/file "/Volumes/Ambly-303F68E9"))returnsfalse.