Fix parsing for mountinfo and related fields when presented with empty fields#357
Merged
Fix parsing for mountinfo and related fields when presented with empty fields#357
Conversation
…y fields Issue #333 found a case where some fields in mount-related files contain a totally empty field (which can look like two consecutive spaces in files that have space-delimited fields). This general fix is to use `split(' ')` instead of `split_whitespace()` since the former does not collapse consecutive spaces
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
1 participant
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.
Issue #333 found a case where some fields in mount-related files contain a totally empty field (which can look like two consecutive spaces in files that have space-delimited fields).
This general fix is to use
split(' ')instead ofsplit_whitespace()since the former does not collapse consecutive spaces