-
Notifications
You must be signed in to change notification settings - Fork 164
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.
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
v1.5.0 I am still getting that the CPU Quota is not defined. #49
Comments
The code is public domain if someone wants to look at what I'm running. I am using the latest version v0.12 of KIND and the recommended container. https://github.com/ardanlabs/service https://github.com/ardanlabs/service/blob/master/app/services/sales-api/main.go |
@ardan-bkennedy - Yes the merged version seems to have issues. Probably, I will be able to take a look at it 'til the end of the day. |
Brilliant and thanks for all the attention on this. Very much appreciated. |
Thanks for the report @emadolsky @ardan-bkennedy! The point where it decides between cgroups2 and 1 is here: automaxprocs/internal/runtime/cpu_quota_linux.go Lines 63 to 70 in 2e85815
But I think the issue is here: automaxprocs/internal/cgroups/cgroups2.go Lines 91 to 94 in 2e85815
We made a small mistake there with the refactoring: we turned "if any of the mount points meet this condition" to "if the last mount point meets this condition". The tests didn't catch it because the test mountinfo file has a single entry. We'll get this fixed and push a patch release ASAP. |
Fix released. Thanks for flagging this @emadolsky @ardan-bkennedy! |
Brilliant. Can't wait to test it later today!! |
YES!!! This is working!!! THANK YOU! |
Add an example of uber-go/automaxprocs which is used by lots of applications to avoid CPU throttling. Related to uber-go/automaxprocs#49
Add an example of uber-go/automaxprocs which is used by lots of applications to avoid CPU throttling. Related to uber-go/automaxprocs#49
I'm still having this problem with 1.5.3 😭😭😭😭😭😭 |
Originally posted by @ardan-bkennedy in #44 (comment)
The text was updated successfully, but these errors were encountered: