[Octave-bug-tracker] [bug #49203] File visible in File Browser, but interpreter can't see it right away when on network drive

[Nicholas Jankowski]

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

Summarizing some offline discussion with the discoverer of the bug (Bradley,
on email distribution):

The originator of the bug has been able regularly recreate the issue.
screenshot.png is attached.

extracted from the screenshot:

User has an existing function test42. Octave sees the function and runs it
without trouble. Verifies he can run it and gets the local folder modified
date with:


>> test42; dirinfo = dir (pwd); disp(ctime(dirinfo(3).statinfo.mtime))
b = 8882443
Mon Oct 24 14:25:26 2016 


user edits the file to verify that Octave picks up the change:


>> edit test42   **resaves the file
>> test42; dirinfo = dir (pwd); disp(ctime(dirinfo(3).statinfo.mtime))
b = 8882443
Mon Oct 31 09:43:57 2016

everything works as expected.  

Now, user creates a new file, and Octave doesn't see it or an updated modified
date:


>> test43; dirinfo = dir (pwd); disp(ctime(dirinfo(3).statinfo.mtime))
error: 'test43' undefined near line 1 column 1
>> dirinfo = dir (pwd); disp(ctime(dirinfo(3).statinfo.mtime))
Mon Oct 31 09:43:57 2016

>> edit test43  **resaves test43
>> dirinfo = dir (pwd); disp(ctime(dirinfo(3).statinfo.mtime))
Mon Oct 31 09:43:57 2016

>> test43; dirinfo = dir (pwd); disp(ctime(dirinfo(3).statinfo.mtime))
error: 'test43' undefined near line 1 column 1


Note that in the screenshot and as reported by the user, test43 shows up
immediately as expected in the File Browser, and the edit function doesn't
fail. So, the file is present, visible, and accessible.  But for some reason
either mtime is not being updated, or Octave is not seeing it as updated. 

I was able to create this on my network only once (see discussion below) and
not since. I suspected it was a latency issue that was just delaying my PC
seeing the updated modify time, as it always did eventually see the new file.

The user reports that no matter how long he waits, Octave never 'sees' the new
file, which it seems means it never sees an updated mtime, until he closes and
reopens Octave.

(file #38845)
    _______________________________________________________

Additional Item Attachment:

File name: screenshot.png                 Size:66 KB


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?49203>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/