[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #49203] File visible in File Browser, but inte

From: Nicholas Jankowski
Subject: [Octave-bug-tracker] [bug #49203] File visible in File Browser, but interpreter can't see it right away when on network drive
Date: Mon, 31 Oct 2016 20:36:21 +0000 (UTC)
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0

Follow-up Comment #16, bug #49203 (project octave):

my Google-fu seems to inform me that this could be stemming from a number of

"Time stamps are updated at various times and for various reasons. The only
guarantee about a file time stamp is that the file time is correctly reflected
when the handle that makes the change is closed." [1]

how might this relate to files created in the editor? Might it explain why he
has to close and reopen Octave for it to look for the new file?

"Explorer gets is information from NTFS, by using a cmd prompt and “dir”
we found that the NTFS metadata for the files is not updated until the handle
to a file is closed.

Refreshing the information of a FOLDER is just going to go to the (memory
resident) metadata cached by NTFS, but querying the file explicitly will force
disk I/O to get the properties – this was a design change introduced in
Vista to reduce unnecessary disk I/O to improve performance" [2]

(that last is from a 2010 post getting comments for years...)

Seems that Windows Server, and or Windows OS's have options that could render
use of 'Date Modified' as unreliable for function checking (if disk I/O
optimization is the reason, I can see why this only really surfaced for
network drives).

If this is the case, then this would appear to require significant effort. are
there any workarounds or alternatives that jump to the mind of those familiar
with Octave's inner workings?  (Workarounds would be nice if this is going to
be relegated to "WTF Windows... won't fix")




Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]