One urgent bug in complex type decoding and two issues for the JSON encoder were found in the latest release:
- The output of the Pubsub JSON encoder namespace Uri for servers which use a not well formed namespace Uri added a http:// prefix, while the previous implementation passed the non well formed Uri along. To preserve the existing behavior, the change was reverted.
- WriteStatusCode in the JSON encoder could produce invalid JSON when used with NonReversible/Verbose encoding.
- A new issue was found when a complex type contains an empty array (length -1), the binary decoder fails to decode the type with a BadDecodingError.
What's Changed
- Fix ExpandedNodeId.Format output for not well formed uri and JSON Ver… by @mregen in #2795
- Null pointer exception when reading a complex type with empty arrays.… by @marcschier in #2799
Full Changelog: 1.5.374.124...1.5.374.126
Contributors
mregen and marcschier