-
Notifications
You must be signed in to change notification settings - Fork 897
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 rake evm:status
and evm:status_full
#17054
Fix rake evm:status
and evm:status_full
#17054
Conversation
@miq-bot add_label bug |
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.
thnx nick
SCREW YOU @miq-bot ! I KNOW WHAT LOOKS GOOD!!1! ❗️ ❗️
|
83f15bc
to
26ad721
Compare
Okay, made the testing for this less brittle, so travis should now pass 😓. These tests #Suck™, and it sucks that I am testing what gets sent to Anyway, my plan is to make |
@NickLaMuro the width of the columns are variable based upon the input. If you want to avoid tabelize (which does have tests by the way) I'd use strs.map { |str| "%-*s" % [strs.map(&:length).max, str] } |
@kbrock right, I realized the variable width of the columns after I started looking into it "for real-sies".
yeah, I figured. Mostly wanted someone to see the heredocs and be like "oh, okay, that is what it is supposed to look like". Ideally, the methods that provide the data to Didn't want to do that refactoring as part of this PR, but now thinking that adding the tests is just too brittle... |
26ad721
to
5b40504
Compare
After a botched rebase (allegedly), the evm status commands became unusable since the scope for the `mb_usage` and `mb_threshold` was in the incorrect block. This fixes that, as well as adds some tests to make this quicker to catch instead of letting our users find out for themselves.
Some comments on commit NickLaMuro@5b40504 spec/lib/tasks/evm_application_spec.rb
|
Checked commit NickLaMuro@5b40504 with ruby 2.3.3, rubocop 0.52.0, haml-lint 0.20.0, and yamllint 1.10.0 spec/lib/tasks/evm_application_spec.rb
|
After a botched rebase (allegedly), the evm status commands became unusable since the scope for the
mb_usage
andmb_threshold
was in the incorrect block.This fixes that, as well as adds some tests to make this quicker to catch instead of letting our users find out for themselves.
Links
Steps for Testing/QA
Confirm we aren't crazy by trying to run
rake evm:status
on master, then checkout these changes and do the same.