[6.3 🍒] Switch to lossy UTF8 decoding for dependency scanner diagnostic result strings#2081
Open
artemcm wants to merge 1 commit intoswiftlang:release/6.3from
Open
[6.3 🍒] Switch to lossy UTF8 decoding for dependency scanner diagnostic result strings#2081artemcm wants to merge 1 commit intoswiftlang:release/6.3from
artemcm wants to merge 1 commit intoswiftlang:release/6.3from
Conversation
…t strings The 'toSwiftString' code currently force-unwraps a 'String' initializer which attempts to decode the input buffer as valid UTF-8. We have seen a crash on this force-unwrap. This change switches 'toSwiftString' to use the Swift standard library's 'String(decoding:,as:)' instead of Foundation's 'String(data:,encoding:)'. The former returns a non-optional value which replaces non-UTF-8 characters with a Unicode replacement character, instead of failing and returning 'nil'. This will not only resolve the crash, but also result in us emitting these potentially-corrupted strings for the user to see. Resolves rdar://157486211
Contributor
Author
|
@swift-ci test |
nkcsgexi
approved these changes
Feb 11, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Cherry-pick of #2080
Explanation
The toSwiftString code currently force-unwraps a String initializer which attempts to decode the input buffer as valid UTF-8. We have seen a crash on this force-unwrap.
This change switches toSwiftString to use the Swift standard library's String(decoding:,as:) instead of Foundation's String(data:,encoding:). The former returns a non-optional value which replaces non-UTF-8 characters with a Unicode replacement character, instead of failing and returning nil.
This will not only resolve the crash, but also result in us emitting these potentially-corrupted strings for the user to see.
Resolves: rdar://157486211
Main branch PR: Switch to lossy UTF8 decoding for dependency scanner diagnostic result strings #2080
Risk: Low, this change removes a force-unwrap which was previously hit when encountering non-UTF8 strings in the dependency scanner output. It replaces it with a lossy conversion method which will not crash when encountering such invalid strings.
Reviewed By: TBD
Testing: Tests added to the driver test suite to validate the new logic results in the driver no longer crashing on invalid UTF8 dependency scanner output.