Skip to content

Issues: uber-go/automaxprocs

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

11 Open 21 Closed
11 Open 21 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

pls public the internal/cgroups package
#86 opened Dec 12, 2023 by kkHAIKE
is not a descendant of mount point root
#85 opened Nov 24, 2023 by wjsshide
3
How does it work? How does it automatically set the value of GOMAXPROCS based on the cgroup?
#84 opened Nov 23, 2023 by JokerDevops
Doesn't work on ECS (nested cgroups)
#66 opened Apr 29, 2023 by blampe
2
Support for soft RAM limit?
#56 opened Aug 3, 2022 by pete-woods
6
What happens if cpu quota on k8s side is less than 1 core?
#54 opened Apr 14, 2022 by timo-klarshift
7
qurying memory quota not work when /proc/self/mountinfo match multiple keywords
#41 opened Jul 19, 2021 by coco-roll
no cgroup mountinfo in /proc/self/mountinfo if shareProcessNamespace=true
#38 opened May 13, 2021 by stonewesley
Provide an API to expose the read value without setting GOMAXPROCS
#29 opened Jul 15, 2020 by ajwerner
3
Message change on upgrade to 1.2.0
#20 opened Nov 22, 2019 by eccles
1
The log format should be configurable or customizable
#18 opened Jul 12, 2019 by xdlai
5
ProTip! Find all open issues with in progress development work with linked:pr.