[release/8.0-staging] Stop trying to format HOST_RUNTIME_CONTRACT property with locale settings #97891
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.
Partial backport of #95801 to release/8.0-staging - skips the changes to utils for ends_with / starts_with.
Customer Impact
Reported in:
In environments with certain locale settings, the runtime fails to initialize due to an incorrect runtime property. The host passes a runtime contract pointer as a property to the runtime, but it is incorrectly formatting it based on locale settings. The fix switches the computation of the property to use a function that is non-locale-dependent (stops using stringstream in favour of printf).
Regression
This is a new property in 8.0. It used the same mechanism that was used a different property in past releases (which would have the same issue), but that was only for single-file. In this case, it is for general initialization.
Testing
Manual
Risk
Low