Empty file in FS.stat or FS.read directly after FS.write about q-io HOT 2 CLOSED

There’s no Stat cache in Q-IO; we call into Node.js directly and just wrap stat with a promise. I find it unlikely that Node.js has a cache either. However, if there were a cache at either layer, I think you could expect the stat to be up-to-date immediately (having been found in the cache), and the new problem would be how to invalidate that cache if another process changes the file system. We could conceivably fix the problem if the user expressed that they were sure that they were the only program touching a branch of the file system and introduce caching in that case, but that’s more complexity than I’m willing to take on.

It is very likely that this is an issue with the underlying operating system and file system, but, as they say, select is not broken.

from q-io.

Thanks for the info.

I'm on windows which has the occasional issue with node so it is hard to be 100% sure it is my own code or not (what I'm doing looks so simple... :)

But at least we can assume the problem is not in q-io. I'll close this for now.

from q-io.