-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Fix --memory flag parsing in minikube start #9033
Conversation
Hi @vixus0. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: vixus0 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Travis tests have failedHey @vixus0, 1st Buildmake test
TravisBuddy Request Identifier: 0ed2c5b0-e21b-11ea-81c3-ef1e647c3fbd |
Travis tests have failedHey @vixus0, 1st Buildmake test
TravisBuddy Request Identifier: 3e821bd0-e21b-11ea-81c3-ef1e647c3fbd |
Can one of the admins verify this patch? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thank you very much @vixus0 for fixing this bug, do you mind sharing the output of After this PR in the description?
also would u please run "make lint" and address the lint issue?
@medyagh I've updated the description, I hope that works. When I tried
|
@vixus0 - You should be able to fix the lint error by running |
Odd that We do have an alternative linter in the Makefile, but it does raise a few other issues that would not be related to your PR: |
you can fix that by
|
Due to the way Go handles variable scope, `mem` was being redeclared inside the conditional. Outside, we were stuck with the value provided by `suggestMemoryAllocation`, therefore ignoring the value passed through the `--memory` flag.
@medyagh lint issue should be fixed. Still couldn't get |
any timeline on another point release to get this fix out? |
@ThisGuyCodes v1.13.0 will be released this week. |
Fixes #9017. Due to the way Go handles variable scope,
mem
was being redeclared inside the conditional. Outside, we were stuck with the value provided bysuggestMemoryAllocation
, therefore ignoring the value passed through the--memory
flag.Output of
minikube start
with the fix: