go.mod: bump procfs to 0.16.1, go mod tidy #3337
Open
Conversation
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
Signed-off-by: Michael Fuller <[email protected]>
mfuller-lambda
force-pushed
the
mfuller-lambda/procfs_0_16_1
branch
from
72eeb1d to
83b2241
Compare
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.
Should help nudge closer to resolving #3265
Tested a fresh build of node_exporter using this branch on one of our hardware configurations seeing issues, and can confirm it looked better.
I'm not sure there's any particular release schedule this could be pulled into, but pinging @SuperQ and @discordianfish for a review of this and to check if there is any possibility to roll a new version with this included 🙏 (and, thank you in advance for your time to review and respond!)