ensure we can handle non-utf8 string arg values in the deprecator #18224
+2
−0
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
Steps to reproduce:
ddev craft test-plugin/default/testIt can also be achieved if
$t1is set to e.g.random_string(5).Technically, this can also be reproduced by calling
Json::encode()on a string that contains non-UTF8 chars.Fix:
Running the stack trace string-type argument values via
mb_convert_encoding()ensures the stack trace can be properly saved in the database.Related issues
#18218