quota 有可能为 "max"
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 62/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- go
- Domain
- operating-systems
Research direction
Start in core/system/cpu_cgroup_v2.go at the linked line and compare the quota handling with the cgroup v2 documentation. Confirm that quota may be the string "max" as well as a floating-point value, then verify that both forms are handled correctly and that the existing CPU quota behavior remains intact.
Written by the indexing model from the issue text.
Description
- Dominant language
- Go
- Stars
- 63
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from bytedance/pid_limits
-
积分项计算方式 Open
Difficulty 2/5 1-3 hours Newbie friendliness 42/100
bytedance/pid_limits#6 ·
All issues in bytedance/pid_limits
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
enhancement needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
kind/cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes-sigs/kueue#15947 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100