View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0009096CTT UA Test CaseApi Changepublic2023-08-11 12:492024-04-23 16:02
Reporterjb Assigned ToPaul Hunkar  
PrioritynormalSeverityminorReproducibilityhave not tried
Status assignedResolutionopen 
Summary0009096: Typo in eventQueueOverFlowCount in SubscriptionDiagnosticsDataType
Description

According to https://reference.opcfoundation.org/Core/Part5/v104/docs/12.15 the element eventQueueOverFlowCount in the datatype SubscriptionDiagnosticsDataType is written with an uppercase "F" in "overflow". Other fields like "monitoringQueueOverflowCount" or the event "EventQueueOverflowEventType" are written with lowercase "f". Besides the BrowseNames of the component variables Variable_SubscriptionDiagnosticsType_EventQueueOverflowCount (i=8902) and Variable_SubscriptionDiagnosticsArrayType_SubscriptionDiagnostics_EventQueueOverflowCount (i=12815) are written with a lowercase "f", too. I suppose that the uppercase "F" in the datatype is a typo that prevents automatic matching of datatype-fields and properties/components of variables.

TagsNo tags attached.
Files Affected

Relationships

related to 0003909 closedRandy Armstrong NodeSets, XSDs and Generated Code Wrong BrowseName for EventQueueOverflowCount 
related to 0009120 closedJeff Harding 10000-005: Information Model Typo in eventQueueOverFlowCount in SubscriptionDiagnosticsDataType 
related to 0009121 closedRandy Armstrong NodeSets, XSDs and Generated Code Typo in eventQueueOverFlowCount in SubscriptionDiagnosticsDataType 

Activities

Paul Hunkar

2023-08-17 16:23

administrator   ~0019898

This appear to be a nodeset issue - until that is resolved testing can do nothing - wait for feedback from Randy

Paul Hunkar

2023-08-20 04:34

administrator   ~0019907

from discussion with Randy -
regarding related closed issue
"ok - this issue was closed after the 1.04 RC but before its release
seems like it was reported on 1.03 because that was only released version at the time
it was fixed in in 1.03 but we forget to fix the 1.04 RC
which then caused the issue to propagate to 1.05
we should Errata 1.04 and 1.05 to match 1.03
this is the least invasive change
clone the issue to 1.04, 1.05 nodesets and part 5"

Jim Luth

2023-08-22 18:50

administrator   ~0019911

Agreed to make breaking changes to 1.04 and 1.05 to match 1.03 that is already correct. Scheduled for 1.05.04 and the next 1.04 Errata. Cloned to Part 5 and Nodeset.

Issue History

Date Modified Username Field Change
2023-08-11 12:49 jb New Issue
2023-08-17 16:23 Paul Hunkar Note Added: 0019898
2023-08-17 16:23 Paul Hunkar Status new => acknowledged
2023-08-17 16:23 Paul Hunkar Relationship added related to 0003909
2023-08-20 04:34 Paul Hunkar Note Added: 0019907
2023-08-22 18:50 Jim Luth Note Added: 0019911
2023-08-22 18:50 Jim Luth Assigned To => Paul Hunkar
2023-08-22 18:50 Jim Luth Status acknowledged => assigned
2023-08-22 18:54 Jim Luth Issue cloned: 0009120
2023-08-22 18:54 Jim Luth Relationship added related to 0009120
2023-08-22 18:59 Jim Luth Issue cloned: 0009121
2023-08-22 18:59 Jim Luth Relationship added related to 0009121
2024-04-23 16:02 Paul Hunkar Project Specifications => CTT UA Test Case
2024-04-23 16:02 Paul Hunkar Category Spec => Api Change