bugGNU Octave - Bugs: bug #61840, Octave gives wrong (misleading)...

 
 

bug #61840: Octave gives wrong (misleading) error message when API version is not current

Submitted by:  None
Submitted on:  Mon 17 Jan 2022 11:49:36 AM UTC
 
Category:  Interpreter Severity:  2 - Minor
Priority:  3 - Low Item Group:  Unexpected Error or Warning
Status:  None Assigned to:  None
Originator Name:  Bernhard Schweighofer Originator Email:  -email is unavailable-
Open/Closed:  * Open Release:  * dev
Operating System:  * Any
* Mandatory Fields

Add a New Comment (Rich Markup)
   

Comment Type & Canned Response:
       

 

Wed 19 Jan 2022 04:00:52 PM UTC, comment #4: 

Reducing Priority and Severity of bug since this is now simply about finding a good informational message.

Rik <rik5>
Project Administrator
Tue 18 Jan 2022 06:03:17 PM UTC, comment #3: 

@Pantxo: No, you are right. Cases like the one here were part of the reason why packages will be installed in an API-specific location (by default).

A user could still change the installation prefix though.
If someone would like to come up with an implementation for a better error message for that case, I'm happy to review patches. (But, re-setting the installation prefix to an API independent location might be self-inflicted pain imho...)

Markus M├╝tzel <mmuetzel>
Project Member
Tue 18 Jan 2022 05:27:13 PM UTC, comment #2: 

From the upcoming Octave 7 on, packages are installed in a version (API) specific directory. So my conclusion is that Octave won't see outdated packages anymore and this issue won't happen again. Am I wrong?

Pantxo Diribarne <pantxo>
Project Member
Mon 17 Jan 2022 10:18:45 PM UTC, comment #1: 

Yes, I have seen this previously with something else in signal. I have learned that if it suddenly says it can't find a function that worked last week, I should do "pkg install" again.

Do you have a suggestion for the wording of the error you wish to see?

Anonymous
Mon 17 Jan 2022 11:49:36 AM UTC, original submission:  

Got the following error message when I tried to execute 'medfilt1' (from the signal package / octave forge):

error: 'medfilt1' undefined near line 1, column 1

The 'medfilt1' function belongs to the signal package from Octave
Forge but has not yet been implemented.

Please read <https://www.octave.org/missing.html> to learn how
you can contribute missing functionality.

But, the medfilt1 function is already implemented! I'm using the signal package version 1.4.1 and it is loaded... So I took a deeper look into the problem.
Going to the directory where the medfilt1 file is located (~/octave/signal-1.4.1/x86_64-pc-linux-gnu-api-v55) and again executing 'medfilt1', I got a different error message:

error: API version api-v55 found in .oct file function 'medfilt1'
       does not match the running Octave (API version api-v56)
       this can lead to incorrect results or other failures
       you can fix this problem by recompiling this .oct file

Now this error message does make sense. I reinstalled the signal package (pkg install -forge signal) which forced a recompile. The x86_64-pc-linux-gnu-api-v55 subdirectory in the signal-1.4.1 directory changed (as expected) to ...-v56 and now all works fine.

So in the end, the initial error-message was completely misleading. Maybe somebody can fix this?

kind regards
Bernhard

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 mmuetzel (Posted a comment)
  • -email is unavailable- added by pantxo (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 project members can vote.

     

     

     

     

    Follow 6 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2022-02-02 rik5 SummaryOctave gives wrong (misleading) error message => Octave gives wrong (misleading) error message when API version is not current
    2022-01-19 rik5 Severity3 - Normal => 2 - Minor
        Priority5 - Normal => 3 - Low
    2022-01-18 mmuetzel Release6.4.0 => dev
        Operating SystemGNU/Linux => Any
    2022-01-18 mmuetzel CategoryNone => Interpreter

    Back to the top


    Powered by Savane 3.9