Opened 6 years ago

Last modified 6 years ago

#5048 closed defect

Wrong error messages — at Version 8

Reported by: massimo ceraolo Owned by: Adeel Asghar
Priority: blocker Milestone: 1.14.0
Component: OMEdit Version:
Keywords: Cc: Adrian Pop

Description (last modified by massimo ceraolo)

I suppose a program user should take seriously error and warning messages to avoid bigger issues.
Therefore I suppose any false error message should be corrected.

In this ticket I describe a few error messages that are probably invalid.

1) opening message under Linux
message when opening OMEdit under linux (OMEdit 1.13.0~dev-137-g0e9c2ff
Connected to OpenModelica 1.13.0~dev-1195-g6d891ea)
When I open OMEdt I receive the following error message:

[1] 03:46:50 Scripting Error
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile

I don't know what this means and implies. I would say that this massage has no impact on the user's experience: I think it should be either be removed or made clearer for the final user.

2) message when duplicating (tested on Connected to OpenModelica 1.13.0~dev-1195-g6d891ea under Linux, and on OMEdit v1.13.0-dev-113-g8c6364e6 (64-bit)
Connected to v1.13.0-dev-640-gff8188090 (64-bit) under Windows)

Currently OMEdit shows a strange message whenever we duplicate a model in a package.
The issue can be replicated considering the attached Test.mo.
If we duplicate RL1 giving for instance to the duplicated class the name RL2, I receive the following error message:

[1] 21:18:40 Syntax Error
[: 1:0-1:0]: No viable alternative near token: C

[2] 21:18:40 Translation Error
[: 0:0-0:0]: Internal error Failed to scan top of input: EOF
  Expected one of: <EOF>
  Current parse tree is:   The parser stack is:

It seems to me that no error occurred while duplication. So, probably this error message is just wrong

3) Opening file under Linux (tested on OMEdit 1.13.0~dev-205-g65f0077
Connected to OpenModelica 1.13.0~dev-1371-gc7f4444)
Open test.mo file using Open Model/Library Files(s) menu command.
The following error message is displayed in red:

[1] 09:03:39 Scripting Error
Gtk-Message: 09:03:35.599: GtkDialog mapped without a transient parent. This is discouraged.

It seems a false error, which is not displayed when loading the same file from the recent Files list.
BTW, I don't understand the meaning of this message, but I would say that something that is just discouraged should be more a warning than an error.

4) flange_a falsely reported as missing
If we open Modelica.Mechanics.Translational.Examples.Friction in diagram mode we don't see flanges on stop1 and stop2. If we simulate it we get the following error messages:

[1] 08:53:49 Scripting Error
Unable to find component stop2.flange_a while parsing connection {spring.flange_b,stop2.flange_a,}.

[2] 08:53:49 Scripting Error
Unable to find component stop1.flange_a while parsing connection {force.flange,stop1.flange_a,}.

Nevertheless, the model compiles and runs correctly. Using Dymola we do see flanges on stop1 and stop2, and don't see any error message.

5) Opening message under Mac OS
The issue is described in ticket #5122.
As far as I remember also this is a false error since, despite it, OM works normally (cannot check now because currently my Mac installation is broken).

Change History (9)

by massimo ceraolo, 6 years ago

Attachment: Test.mo added

comment:1 by massimo ceraolo, 6 years ago

Summary: False errorFalse error message?

comment:2 by massimo ceraolo, 6 years ago

Description: modified (diff)

comment:3 by massimo ceraolo, 6 years ago

Description: modified (diff)
Summary: False error message?Wrong error messages

comment:4 by Francesco Casella, 6 years ago

Component: *unknown*OMEdit
Owner: changed from somebody to Adeel Asghar

comment:5 by massimo ceraolo, 6 years ago

Description: modified (diff)

comment:6 by massimo ceraolo, 6 years ago

Description: modified (diff)

comment:7 by Francesco Casella, 6 years ago

Priority: normalblocker

We should try as hard as we can to get rid of these bogus messages in the release version, so I mark this as blocker lest we forget about it.

The new API, which should be pushed in by @adrpo as soon as possible could also help solving the problem.

comment:8 by massimo ceraolo, 6 years ago

Description: modified (diff)
Note: See TracTickets for help on using tickets.