fix(inputs.gnmi): Handle base64 encoded IEEE-754 floats correctly #17278
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Currently base64-encoded bytes (aka
BytesVal
) are decoded into strings despite the fact that the result might contain non-ASCII or even non-UTF8 characters. As these values often do contain float32 values, the PR tries to decode them as float and, if the prerequisites are not given, reencodes the values into Base64 to ensure printable field values.Checklist
Related issues
resolves #15046
resolves #16365
resolves #17154