Make use of hex string instead of FDB printable to remove test failures because of special characters #2405
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…es because of special characters
Contributor
Result of fdb-kubernetes-operator-pr on Linux RHEL 9
|
nicmorales9
reviewed
Dec 16, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Description
We've seen a few cases in our nightly testing where the tests have failed because of a special character in the value, e.g. a semicolon (
;) where thefdbclicommand thought the current command is split. Using only the hex format is a better approach to prevent those failures.Type of change
Discussion
Testing
Ran the test manually.
Documentation
Follow-up