feat(ironic): patch for proliantutils for ipmi response to force utf-8 response. #1378
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
RSabounds
changed the title
…unctional issues.
RSabounds
force-pushed
the
ilo-ipmi-utf-8-call-support
branch
from
ee95ef7 to
c311077
Compare
cardoe
approved these changes
Nov 6, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Proliant has an issue of sub-processing, however the response may result in UTF-8 or Latin-1 depending on system. .decode() defaults to UTF-8 and error-handling is FORCED. Adding this resolves the issue by ensuring UTF-8 response.