Fix mountinfo parsing to handle entries with 10 fields#282
Merged
pgier merged 1 commit intoprometheus:masterfrom Apr 30, 2020
Merged
Fix mountinfo parsing to handle entries with 10 fields#282pgier merged 1 commit intoprometheus:masterfrom
pgier merged 1 commit intoprometheus:masterfrom
Conversation
Signed-off-by: Trey Dockendorf <tdockendorf@osc.edu>
Contributor
Author
|
Any possibility of getting this merged so that node_exporter can incorporate this fix? |
discordianfish
approved these changes
Apr 28, 2020
Member
pgier
approved these changes
Apr 30, 2020
Collaborator
pgier
left a comment
pgier
left a comment
There was a problem hiding this comment.
lgtm, thanks for fixing this!
remijouannet
pushed a commit
to remijouannet/procfs
that referenced
this pull request
Oct 20, 2022
Fix mountinfo parsing to handle entries with 10 fields
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
3 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.
See prometheus/node_exporter#1673 for the full context of how this is impacting node_exporter.