T
Twisted
I'm seeing several examples of broken behavior with java.io.File():
* mkdirs() sometimes returns false, despite succeeding (the directories
exist afterward on the
filesystem)
* exists() and isDirectory() sometimes return false when called on a
File object right after a
mkdirs() after which the directory and its parents existed, as
observed using Winblows
Exploder.
What is going on here? Is there even a way to test for the existence of
a directory with 100% accuracy?
* mkdirs() sometimes returns false, despite succeeding (the directories
exist afterward on the
filesystem)
* exists() and isDirectory() sometimes return false when called on a
File object right after a
mkdirs() after which the directory and its parents existed, as
observed using Winblows
Exploder.
What is going on here? Is there even a way to test for the existence of
a directory with 100% accuracy?