improve: get cpu number in container #340
Merged
+29
−29
Conversation
This file contains 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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #340 +/- ##
========================================
Coverage 40.00% 40.00%
========================================
Files 53 53
Lines 3035 3035
========================================
Hits 1214 1214
Misses 1691 1691
Partials 130 130 ☔ View full report in Codecov by Sentry. |
AlexStocks
approved these changes
Jan 9, 2022
ztelur
approved these changes
Jan 11, 2022
bobtthp
pushed a commit
to bobtthp/dubbo-go-pixiu
that referenced
this pull request
Dec 12, 2022
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 this PR does:
Optimize the method of getting the number of cpu in the container
Which issue(s) this PR fixes:
Fixes #313
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
NONE