-
Notifications
You must be signed in to change notification settings - Fork 651
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
add the minimum resource error improvement #2950
base: main
Are you sure you want to change the base?
Conversation
Codecov Report
@@ Coverage Diff @@
## main #2950 +/- ##
==========================================
+ Coverage 86.89% 86.90% +0.01%
==========================================
Files 231 231
Lines 12042 12061 +19
==========================================
+ Hits 10464 10482 +18
- Misses 1578 1579 +1
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
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.
Hey @georgeliao!
Thanks for this!
I kind of feel that instead of making a call to prepopulate an error message that may or not happen, it may be better to modify BlueprintMinimumException
to accept the limits
YAML::Node
instead and let it be responsible for constructing the error message when needed. I hope this makes sense 🙂
@townsend2010 |
The comment is addressed. Please also feel free to comment further if there are still things to improve. The current output of the program is:
|
…And implementation and fix format
…call into BlueprintMinimumException class.
9313938
to
683b5a3
Compare
fixes #2925
This is still a draft implementation, be free to give your comments on it.
The current output error message is like
./multipass launch docker --name load-test --cpus 1 --memory 2G --disk 20GiB