Yes, thatâs true, but (I think) the problem here is that the monitor is being
created without there being a valid stat object, so the stat comparison never
changes. I think that if it was at least initially populated with some stat,
subsequent checks would detect it.
> On Mar 17, 2018, at 2:
Unless the action is atomic, there is still no guarantee that the path will
exist between the time you check and when you set the monitor.
Sent from Yahoo Mail on Android
On Sat, Mar 17, 2018 at 12:28 PM, H. William Welliver
III wrote: Iâve noticed that when using
Filesystem.Monitor on
Iâve noticed that when using Filesystem.Monitor on a system with inotify there
is the possibility of monitors being created on paths that donât exist.
Specifically, if a directory is created and deleted in very rapid succession,
the inotify events are processed after the directory is alread
