You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Background: in normal use, even when one only reads from a filesystem, there is still one property that is modified: the atime property of files and directories. This of course is not the case when a filesystem is mounted read-only, or mounted with the noatime option on Linux.
Because one might use mock-fs to test a tool depends on all properties of items remaining stable (e.g. something that creates a tarball) it would be useful to emulate this noatime behaviour so that subsequent accesses produce exactly the same results.
Could this be achieved by an option that replaces Item.setATime() with a no-op?
The text was updated successfully, but these errors were encountered:
Background: in normal use, even when one only reads from a filesystem, there is still one property that is modified: the
atime
property of files and directories. This of course is not the case when a filesystem is mounted read-only, or mounted with thenoatime
option on Linux.Because one might use
mock-fs
to test a tool depends on all properties of items remaining stable (e.g. something that creates a tarball) it would be useful to emulate thisnoatime
behaviour so that subsequent accesses produce exactly the same results.Could this be achieved by an option that replaces
Item.setATime()
with a no-op?The text was updated successfully, but these errors were encountered: