Closed
Conversation
A null value after the BOM no longer causes an error.
Member
|
@lumeet Sorry for leaving this so long but it no longer applies cleanly. Can you update this PR? |
Contributor
Author
|
@enebo I'm closing this. The bug is fixed by another commit and |
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
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.
...results in...
A check for a null value seems to be missing after the BOM.
The
test_truncate_wbufremoval is just general cleanup. It doesn't have anything to do with the fix. I guess it's ok. :)