View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0005542Compliance Test Tool (CTT) Unified Architecture1 - Script Issuepublic2020-03-19 12:452021-03-25 16:01
ReporterThomas Merk Assigned ToSebastian Allmendinger  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version1.04.09.394 
Fixed in Version1.04.09.398 
Summary0005542: Testing value in type tree and reporting error if NULL
Description

Script Base Information / Base Info Core Structure / 001.js

Attribute.DataType (i=24) or Value (Value: Null, StatusCode: Good (0x00000000), SourceTimestamp: 2020-03-18T15:36:00.174Z,
ServerTimestamp: 2020-03-18T15:36:00.174Z, of current Instance (i=14595) doesn't match the expectation (BuiltInType.)

The mentioned "instance" with NodeId i=14595 is the "PublisherId" below "PubSubConnectionType".
The instances in the type tree do not need a value as far as I know.
The standard nodeset2 XML does not have a value defined at this place...

TagsNo tags attached.
Files Affected

Relationships

related to 0005899 closedSebastian Allmendinger PubSubConnectionType.PublisherId datatype is not specified 
related to 0006113 closedSebastian Allmendinger DataSetReaderType.PublisherId datatype is not specified 

Activities

Thomas Merk

2020-03-19 12:53

reporter   ~0011782

This happens often (for each PubSub connection below "PublishSubscribe" object.
It looks like the NodeId of the type definition is used instead of the NodeId of the property of (connection) instance .

Sebastian Allmendinger

2021-02-25 15:08

developer   ~0013824

Two issues have been identified while investigating this report:
1) There was an issue in the generated JSON file used by the CTT. All validations of variables that have the DataType attribute set to BaseDataType failed due to a missing/invalid DataType declaration.
2) An additional issue has been identified while investigating the printed error message. A wrong variable was used. This did not only lead to a wrong message output, but also that only the InstanceDeclaration was validated instead of the current instance.

Paul Hunkar

2021-03-25 16:01

administrator   ~0014079

reviewed in CMP call - agreed to change and closed

Issue History

Date Modified Username Field Change
2020-03-19 12:45 Thomas Merk New Issue
2020-03-19 12:53 Thomas Merk Note Added: 0011782
2020-03-20 16:04 Paul Hunkar Assigned To => Alexander Allmendinger
2020-03-20 16:04 Paul Hunkar Status new => assigned
2021-02-25 14:05 Sebastian Allmendinger Relationship added related to 0005899
2021-02-25 14:07 Sebastian Allmendinger Relationship added related to 0006113
2021-02-25 15:08 Sebastian Allmendinger Note Added: 0013824
2021-02-25 15:08 Sebastian Allmendinger Assigned To Alexander Allmendinger => Sebastian Allmendinger
2021-02-25 15:08 Sebastian Allmendinger Status assigned => resolved
2021-02-25 15:08 Sebastian Allmendinger Resolution open => fixed
2021-02-25 15:08 Sebastian Allmendinger Fixed in Version => 1.04.09.398
2021-03-25 16:01 Paul Hunkar Status resolved => closed
2021-03-25 16:01 Paul Hunkar Note Added: 0014079