-
Notifications
You must be signed in to change notification settings - Fork 313
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 linting issues reported by make precommit
#838
Comments
@drawlerr some top level guidelines to make the corresponding PRs more manageable to review and focus on important topics:
|
This commit will allow us to make progress on the pylint issues we would like to fix, while allowing users to commit new code that may fail some of these. What ends up happening is that new code can be merged by other users, and if precommit is not run in CI, we might accidentally allow a pylint violation to sneak back in. Removing the pylint check in the branch/PR that is removing these will allow CI to fail the check so the user can get feedback if another person has merged code in that violates the check in the branch/PR. Relates elastic#838
This commit will allow us to make progress on the pylint issues we would like to fix, while allowing users to commit new code that may fail some of these. What ends up happening is that new code can be merged by other users, and if precommit is not run in CI, we might accidentally allow a pylint violation to sneak back in. Removing the pylint check in the branch/PR that is removing these will allow CI to fail the check so the user can get feedback if another person has merged code in that violates the check in the branch/PR. Relates #838
With this commit we reenable the pylint check W0106 which checks whether an expression not a function call is assigned to nothing. Relates #838
With this commit we reenable the pylint check C4002 which checks whether triple quotes are properly formatted. Relates #838
With this commit we reenable the pylint check W0221 which checks whether the correct number of parameters is used in an implemented or overridden method. Relates #838
With this commit we reenable the pylint check W0612 which checks whether a variable is defined but unused. Relates #838
With this commit we reenable the pylint check E1120 which checks whether function calls contain the correct number of arguments. Relates #838
With this commit we reenable the pylint check W0404 which checks whether an import has already been imported. Relates #838
With this commit we reenable the pylint check W0212 which checks whether protected members are used outside of their classes scope. Relates #838
With this commit we reenable the pylint warning `assignment-from-none` which checks whether a `None` return value from a function is assigned to a variable. We also audited all such issues in the code and disabled the warning accordingly. Relates elastic#838
With this commit we reenable the pylint warning `assignment-from-none` which checks whether a `None` return value from a function is assigned to a variable. We also audited all such issues in the code and disabled the warning accordingly. Relates #838
With this commit we re-enabled the pylint check `R0904` which checks for too many public methods. We have eliminated the warnings by using different strategies: * We have merged too fine-grained methods into more coarse-grained ones. * We have eliminated some methods that have only been called once. * We have properly marked protected methods. * Where appropriate we have disabled the warning (in tests). Relates elastic#838
With this commit we re-enabled the pylint check `R0904` which checks for too many public methods. We have eliminated the warnings by using different strategies: * We have merged too fine-grained methods into more coarse-grained ones. * We have eliminated some methods that have been called once or never. * We have properly marked protected methods. * Where appropriate we have disabled the warning (in tests). Relates elastic#838
With this commit we re-enabled the pylint check `R0904` which checks for too many public methods. We have eliminated the warnings by using different strategies: * We have merged too fine-grained methods into more coarse-grained ones. * We have eliminated some methods that have been called once or never. * We have properly marked protected methods. * Where appropriate we have disabled the warning (in tests). Relates #838
With this commit we re-enable the pylint warning `C0415` which checks whether modules are imported outside of the toplevel. While we move most of the imports to toplevel, we keep some imports more targeted, most notable the `elasticsearch` module so we ensure that the library picks up Rally's logging configuration properly even in a (multiprocess) actor system. Relates elastic#838
With this commit we re-enable the pylint warning `C0415` which checks whether modules are imported outside of the toplevel. While we move most of the imports to toplevel, we keep some imports more targeted, most notable the `elasticsearch` module so we ensure that the library picks up Rally's logging configuration properly even in a (multiprocess) actor system. Relates #838
I think we can close this one. |
Now that we got infrastructure to enforce coding conventions in #794 we need to start coming up with PRs to fix issues. This issue tracks the effort and should be only closed when
make precommit
succeeds with no errors reported.The text was updated successfully, but these errors were encountered: