Windows fstat obtains only the file size, then reports a regular-file mode and mtime = 0 for every successful call. The adjacent path-based stat reads actual attributes and last-write time. Querying the same ordinary file through a path and an open handle can therefore report different modification times, even without a concurrent change.
Source evidence at the head of #520:
Acceptance:
Related: #385. Error translation is a separate concern from filling successful metadata.
Audit status: identified by static source inspection; the scenarios above have not been executed during this audit. The permalink fixes the reviewed revision; this report does not claim the defect was introduced by #520.
Windows
fstatobtains only the file size, then reports a regular-file mode andmtime = 0for every successful call. The adjacent path-basedstatreads actual attributes and last-write time. Querying the same ordinary file through a path and an open handle can therefore report different modification times, even without a concurrent change.Source evidence at the head of #520:
pub fun fstatpub fun statAcceptance:
Related: #385. Error translation is a separate concern from filling successful metadata.
Audit status: identified by static source inspection; the scenarios above have not been executed during this audit. The permalink fixes the reviewed revision; this report does not claim the defect was introduced by #520.