Remove psutil patches, prep for bumping psutil to 5.9.0#10544
Merged
Conversation
mx-psi
marked this pull request as ready for review
January 14, 2022 11:47
4 tasks
albertvaka
approved these changes
Jan 14, 2022
albertvaka
left a comment
Contributor
There was a problem hiding this comment.
LGTM if/when the integrations-core PR gets merged.
ofek
approved these changes
Jan 27, 2022
hithwen
approved these changes
Jan 27, 2022
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.
What does this PR do?
Reverts #9577
Motivation
We are bumping psutil to 5.9.0, which includes giampaolo/psutil#2000.
Additional Notes
This needs DataDog/integrations-core#11139. Since we fetch from integrations-core
master, PRs that don't have this change will fail until the rebase/merge main.Describe how to test/QA your changes
Test that the fix applied in #9577 still works.
Reviewer's Checklist
Triagemilestone is set.team/..label has been applied, if known.major_changelabel if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.changelog/no-changeloglabel has been applied.qa/skip-qalabel is not applied.need-change/operatorandneed-change/helmlabels have been applied.