Skip to content

LinuxCommand#verify cleaned up #530

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

Conversation

kvivek1115
Copy link

@kvivek1115 kvivek1115 commented Nov 2, 2019

Description

  • Remove for loop and add case statements in order to humanize the error message and class.
  • LinuxCommand#verify return nil on success and raised the error otherwise.
  • Minor refactoring.
  • Add unit test cases.

Related Issue

Fixes #509

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New content (non-breaking change)
  • Breaking change (a content change which would break existing functionality or processes)

Checklist:

  • I have read the CONTRIBUTING document.

Signed-off-by: Vivek Singh [email protected]

@chef-expeditor
Copy link
Contributor

chef-expeditor bot commented Nov 2, 2019

Hello vsingh-msys! Thanks for the pull request!

Here is what will happen next:

  1. Your PR will be reviewed by the maintainers.
  2. Possible Outcomes
    a. If everything looks good, one of them will approve it, and your PR will be merged.
    b. The maintainer may request follow-on work (e.g. code fix, linting, etc). We would encourage you to address this work in 2-3 business days to keep the conversation going and to get your contribution in sooner.
    c. Cases exist where a PR is neither aligned to Chef InSpec's product roadmap, or something the team can own or maintain long-term. In these cases, the maintainer will provide justification and close out the PR.

Thank you for contributing!

@kvivek1115 kvivek1115 changed the title Wrap known exception in LinuxCommand#verify   LinuxCommand#verify cleaned up Nov 2, 2019
@kvivek1115
Copy link
Author

Hi @zenspider
Could you please have a look and let's know further if any suggestions/feedback?

"sudo: command not found" =>
msg, reason =
case rawerr
when /Sorry, try again/
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why are these regexps?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is no specific to match regex, I only thought of would be nice if we do exact match vs similar one.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, String#=== (what is used under a case/when is an exact match... All of these strings went from "some string" to /some string/, so they went from exact match to a regexp (partial) match. As such, this is looser than before.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@zenspider I do agree with your concern so added minor updates for constructing rawerr and have updated the exact match of string.

"sudo to allow for non-interactive usage.", :sudo_no_tty],
}.each do |sudo, human|
rawerr = human if rawerr.include? sudo
end
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure I'm sold on the benefits of switching this to a case yet. Can you explain this?

That said, I'm REALLY not sold on the each here... it could probably have been a hash lookup? Unless this bit answers the question about why there's regexps now... in which I case I guess I'm sold on the case + regexps.

Copy link
Author

@kvivek1115 kvivek1115 Nov 14, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @zenspider,

Here the only reason for switching to the case is if an exception would occur I would rather say:

I am the one instead of I am one of them

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure I understand that. Assuming my interpretation is correct, then you're doing "I am the one" via raise, not via case vs {...}.each.

res
elsif transport.platform.windows?
res = WindowsCommand.new(transport, options)
res
WindowsCommand.new(transport, options)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thank you!

msg, reason = verification_res
raise Train::UserError.new("Sudo failed: #{msg}", reason)
end
res.verify
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Much better... I like that you're just calling it. Please rename it to verify! to denote that it is a bit more angry now.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@zenspider need your suggestion in order to rename verify to verify!.

As we have base class CommandWrapperBase as a defined methods interface class. and the implementation in LinuxCommand & WindowsCommand classes.

We have the following options to rename verify!:

1. Just rename all the places wherever is used e.i. in CommandWrapperBase, WindowsCommand and LinuxCommand classes.

OR

2. For class LinuxCommand define as an alias method.

alias verify! verify

OR

3. Add verify! method as well in order to make angrier

a) verify should return nil on success and array object when an error occurs

    # (see CommandWrapperBase::verify)
    def verify
      res = @backend.run_command(run("echo"))
      return nil if res.exit_status == 0

      rawerr = res.stdout + " " + res.stderr
        case rawerr
        when /Sorry, try again/
          ["Wrong sudo password.", :bad_sudo_password]
        when /sudo: no tty present and no askpass program specified/
          ["Sudo requires a password, please configure it.", :sudo_password_required]
        when /sudo: command not found/
          ["Can't find sudo command. Please either install and "\
            "configure it on the target or deactivate sudo.", :sudo_command_not_found]
        when /sudo: sorry, you must have a tty to run sudo/
          ["Sudo requires a TTY. Please see the README on how to configure "\
            "sudo to allow for non-interactive usage.", :sudo_no_tty]
        else
          [rawerr, nil]
        end
    end

b) Add verify! and raise an error if occurs.

def verify!
    msg, reason = verify
    return nil unless msg

    raise Train::UserError.new("Sudo failed: #{msg}", reason)
end

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah. Then either 3.b or 4: ignore @zenspider.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added verify! method and updated the PR please have a look again thanks

it "custom error for bad sudo password" do
backend.stubs(:run_command).returns(mock_connect_result("Sorry, try again", 1))
lc = cls.new(backend, { sudo: true })
_ { lc.verify }.must_raise Train::UserError
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

must_raise returns the exception... please test the error message.

Might also want test cases for all of the edge cases covered.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I should add... this can all be refactored into an assertion to make these 1-liners.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay noted, thankyou so much for the feedback, will cover more test cases and update you accordingly.

Copy link
Contributor

@clintoncwolfe clintoncwolfe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm OK with the regexp and case. I would like to see a bit more testing but I think that's coming anyway.

@kvivek1115 kvivek1115 requested a review from a team as a code owner November 18, 2019 11:38
"sudo: command not found" =>
msg, reason =
case rawerr
when /Sorry, try again/
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, String#=== (what is used under a case/when is an exact match... All of these strings went from "some string" to /some string/, so they went from exact match to a regexp (partial) match. As such, this is looser than before.

msg, reason = verification_res
raise Train::UserError.new("Sudo failed: #{msg}", reason)
end
res.verify
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah. Then either 3.b or 4: ignore @zenspider.

"sudo to allow for non-interactive usage.", :sudo_no_tty],
}.each do |sudo, human|
rawerr = human if rawerr.include? sudo
end
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure I understand that. Assuming my interpretation is correct, then you're doing "I am the one" via raise, not via case vs {...}.each.

Vivek Singh added 3 commits November 24, 2019 16:07
 - Minor improvisation & refactoring.
 - Add unit test cases.

Signed-off-by: Vivek Singh <[email protected]>
@kvivek1115 kvivek1115 force-pushed the VSingh/MSYS-1084_clean_up_linux_command_verify branch from c6465b4 to c029473 Compare November 25, 2019 15:06
@codeclimate
Copy link

codeclimate bot commented Nov 25, 2019

Code Climate has analyzed commit c029473 and detected 2 issues on this pull request.

Here's the issue category breakdown:

Category Count
Style 2

View more on Code Climate.

@kvivek1115
Copy link
Author

@zenspider could you please have a look again?

@zenspider zenspider self-requested a review December 4, 2019 23:56
backend.stubs(:run_command).returns(mock_connect_result("Other sudo related error", 1))
lc = cls.new(backend, { sudo: true })
err = _ { lc.verify }.must_raise Train::UserError
_(err.message).must_match(/Other sudo related error/)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

great!


def verify!
msg, reason = verify
return nil unless msg
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For the future: return and return nil have the same effect.

@zenspider zenspider merged commit d94d44d into inspec:master Jan 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Train::Extras::CommandWrapper::LinuxCommand#verify needs to be cleaned up
4 participants