- 
                Notifications
    You must be signed in to change notification settings 
- Fork 799
update PDK template and workflows #1629
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
base: main
Are you sure you want to change the base?
Conversation
29da24a    to
    72fd570      
    Compare
  
    * remove the x86_64 binaries that should not have been added to the repo * mysql_login_path is not supported by MariaDB so skip related tests if the test host doesn't have the binary.
3ee5a50    to
    3aae838      
    Compare
  
    915caa1    to
    7c6c0c8      
    Compare
  
    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.
Reviewed the changes and looks good to me except minor cosmetic comments.
@bastelfreak @smortex can you please also have quick look?
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.
Looks good overall. I added inline comments for 2 tiny things that we may want to think about adjusting.
        
          
                spec/classes/mysql_params_spec.rb
              
                Outdated
          
        
      | context "on #{os}" do | ||
| let(:facts) { facts } | ||
|  | ||
| it { is_expected.to compile } | 
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.
I would expect a private class to not compile 😄 (the commit message of this change is about tests and private classes)
It happen that the class is marked as private in the API but does not call assert_private()…  Do we want to make sure private classes are not directly call and add assert_private() to all classes with @api private?  (I would say yes, as far as I am concerned, but have not checked if this can cause trouble).
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.
I would expect a private class to not compile 😄 (the commit message of this change is about tests and private classes)
Removed
It happen that the class is marked as private in the API but does not call assert_private()… Do we want to make sure private classes are not directly call and add assert_private() to all classes with @api private? (I would say yes, as far as I am concerned, but have not checked if this can cause trouble).
Makes sense to me, but this change is intended to be maintenance only, with no potentially breaking changes.
I'll open another PR for that.
9e28543    to
    10fd765      
    Compare
  
    | @Ramesh7 addressed issues, can you review and merge please? | 
Uh oh!
There was an error while loading. Please reload this page.