Skyline.DataMiner.DataSources.OpenConfig.Gnmi Range 7.x

7.1.2

Fix - Duplicate key errors caused by DataMapper default value handling [ID 45231]

An issue was identified where the DataMapper could perform a FillArray operation containing duplicate primary keys. This was caused by an internal object lacking a proper IEquatable implementation, allowing duplicate entries to exist within a HashSet.

In the observed scenario, this did not impact functionality as the duplicated values were identical. However, it could generate level 0 element logging errors, potentially suggesting incorrect behavior.

7.1.1

Updated version of Skyline.DataMiner.DataSources.CommunicationGatewayMiddleware.OpenConfig used [ID 45162]

The Skyline.DataMiner.DataSources.OpenConfig.Gnmi library has been updated to use version 5.3.4 of Skyline.DataMiner.DataSources.CommunicationGatewayMiddleware.OpenConfig. Previously, it was using version 5.3.0.

7.1.0

Add support for configurable timeouts to GnmiClient operations [ID 43460]

Previously, the Get, Set, and Capabilities calls on a GnmiClient always used a fixed timeout of 5 seconds. These timeout values can now be configured individually per request. If no custom timeout is specified, the default of 5 seconds still applies.

Minimum required version: CommunicationGateway 5.3.0.

7.0.1

Fix - Improved middleware subscription handling in Communication Gateway [ID 42740]

It could occur that the MessageBroker object was disposed of before all middleware subscriptions were disposed of, which could cause threads to get stuck. This will now be prevented.

7.0.0

Fix - DataMapper unable to handle responses where type did not match actual value [ID 42762]

In some cases, it could occur that a response was indicated to be of type Json or JsonIetf, but the actual value was a JSON token instead of a JSON object. The DataMapper was unable to handle this, which caused issues. This has now been resolved.