bugGNU Octave - Bugs: bug #65069, Octave reports .m file undefined...

 
 

bug #65069: Octave reports .m file undefined after creating file on rclone share

Submitter:  None
Submitted:  Thu 21 Dec 2023 08:34:31 AM UTC
   
 
Category:  Interpreter Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Unexpected Error or Warning
Status:  Invalid Assigned to:  None
Originator Name:  Martijn van de Giessen Originator Email:  -email is unavailable-
Open/Closed:  * Closed Release:  * 8.4.0
Operating System:  * GNU/Linux Fixed Release:  None
Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Tue 26 Dec 2023 07:59:42 PM UTC, comment #3: 

This is an upstream issue (rclone).  Octave relies on the timestamp which comes from the operating system and if it isn't being informed about changes to the file system then it isn't it's fault.

Rik <rik5>
Group administrator
Thu 21 Dec 2023 12:35:00 PM UTC, comment #2: 

Thanks. The path(path) workaround indeed works.

Funnily enough, when files are updated, the up to date file is always run. Is there an extra check on the file date?

Would you consider this more of an rclone than an Octave problem? If so, I am happy to consider this bug closed and address it there.

Martijn van de Giessen <mvandeg>
Thu 21 Dec 2023 12:17:23 PM UTC, comment #1: 

Octave uses folder timestamps to determine if a folder needs to be scanned for potentially changed or new .m files.

Your description sounds like the file system on that rclone share doesn't correctly update the folder timestamp when new files are added in that folder.

You could probably work around that by re-initializing the search path after you added a file on that share with the following command:

path(path)


If the timestamps aren't updated when a new file is created, they potentially aren't updated when a file is changed either. So, you might need to manually trigger scanning for changed .m files whenever you change anything in a .m file that Octave already ran before.

If the timestamps on that filesystem are indeed causing this behavior, another workaround would be to move the files to a properly working (local?) filesystem while you are making modifications to them.

Markus Mützel <mmuetzel>
Group administrator
Thu 21 Dec 2023 08:34:31 AM UTC, original submission:  

When creating a new .m file on an rclone share in the Octave GUI, Octave does not recognize the file and report that the function is undefined. After restarting Octave, functionality is as expected.

This behavior can be reproduced as:

>> edit rcloneTest.m # With 'disp "test"' as only line
>> rcloneTest
error: 'rcloneTest' undefined near line 1, column 1
>> exit


Then, restart Octave:

>> rcloneTest
test


I am using the Flathub flatpak version of Octave from 5 November 2023. No other program that I am using shows this behavior, including other flatpaks, hence I am suspecting it is something Octave specific.

The command line version of the Octave flatpak shows the same behavior, reproducible as:


flatpak run org.octave.Octave
<< create and edit testRclone.m with an external editor with 'disp "test"' as only line >>
octave:1> rcloneTest
error: 'rcloneTest' undefined near line 1, column 1
octave:2> exit
<< restart Octave >>
flatpak run org.octave.Octave
octave:1> rcloneTest
test


The rclone version that I am using is:

rclone v1.60.1
- os/version: ubuntu 22.04 (64 bit)
- os/kernel: 6.2.0-39-generic (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.19.3
- go/linking: static
- go/tags: none



Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by rik5 (Posted a comment)
  • -email is unavailable- added by mvandeg (Posted a comment)
  • -email is unavailable- added by mmuetzel (Posted a comment)
  • -email is unavailable- added by None (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only group members can vote.

     

    Follow 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2023-12-26 rik5 StatusNone Invalid
        Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.13-04b1.
    Corresponding source code