Don’t try to add nil
strings to an array.
#408
Merged
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.
This can occur if one or more of the strings in
strarray
is invalid UTF8.We’ve got a user seeing this when we’re pulling in their branch names. The on-disk
.git/refs/*
look ok, but I wonder if there’s something funky going on with the decomposed UTF16 filenames → assumed valid null-terminated UTF8 conversion in@(cStr)
.To wit, I think we should probably not be assuming valid null-terminated UTF8 here, but I’m not sure what we should assume instead.
I haven’t been able to synthesize a failing case (of filename →
nil
string literal) yet.