View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0009121NodeSets, XSDs and Generated CodeApi Changepublic2023-08-22 18:592024-09-10 15:15
ReporterJim Luth Assigned ToRandy Armstrong  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Summary0009121: 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.
Commit Version1.05.04
Fix Due Date2023-10-31

Relationships

related to 0009096 assignedPaul Hunkar CTT UA Test Case Typo in eventQueueOverFlowCount in SubscriptionDiagnosticsDataType 

Activities

Paul Hunkar

2023-08-22 18:59

reporter   ~0019915

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

Paul Hunkar

2023-08-22 18:59

reporter   ~0019916

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:59

administrator   ~0019917

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.

Randy Armstrong

2024-06-13 12:47

administrator   ~0021343

Already fixed.

Jim Luth

2024-06-13 14:57

administrator   ~0021348

Reviewed fix in 1.05.04. Needs 1.04 Errata to close.

Randy Armstrong

2024-06-13 14:58

administrator   ~0021349

Needs 1.04 errata.

Jim Luth

2024-09-10 15:15

administrator   ~0021693

Agreed to 1.04 Errata in Web Meeting.

Issue History

Date Modified Username Field Change
2023-08-22 18:59 Jim Luth New Issue
2023-08-22 18:59 Jim Luth Status new => assigned
2023-08-22 18:59 Jim Luth Assigned To => Randy Armstrong
2023-08-22 18:59 Jim Luth Issue generated from: 0009096
2023-08-22 18:59 Jim Luth Note Added: 0019915
2023-08-22 18:59 Jim Luth Note Added: 0019916
2023-08-22 18:59 Jim Luth Note Added: 0019917
2023-08-22 18:59 Jim Luth Relationship added related to 0009096
2023-08-22 18:59 Jim Luth Project Specifications => NodeSets, XSDs and Generated Code
2023-08-22 18:59 Jim Luth Category Spec => Api Change
2023-08-22 19:00 Jim Luth Commit Version => 1.05.04 RC
2023-08-22 19:00 Jim Luth Fix Due Date => 2023-11-01
2024-06-13 12:47 Randy Armstrong Status assigned => resolved
2024-06-13 12:47 Randy Armstrong Resolution open => fixed
2024-06-13 12:47 Randy Armstrong Note Added: 0021343
2024-06-13 14:57 Jim Luth Note Added: 0021348
2024-06-13 14:58 Randy Armstrong Note Added: 0021349
2024-09-10 15:03 Randy Armstrong Commit Version 1.05.04 RC => 1.05.04
2024-09-10 15:03 Randy Armstrong Fix Due Date 2023-11-01 => 2023-10-31
2024-09-10 15:14 Jim Luth Status resolved => closed
2024-09-10 15:15 Jim Luth Fix Due Date 2023-10-31 => 2023-10-31
2024-09-10 15:15 Jim Luth Note Added: 0021693