Fix pylint warnings
1 unresolved thread
1 unresolved thread
Summary
Addresses #240 (closed)
Four pylint warnings are now ignored, one probable bug fixed
Focus
Are any of the warnings now marked as false positive in fact true positives?
Test Environment
Does the pylint job in the pipeline succeed?
Check List for the Author
-
All automated tests pass -
Reference related issues -
Up-to-date CHANGELOG.md (or not necessary) -
Appropriate user and developer documentation (or not necessary) -
Annotations in code (Gitlab comments)
Check List for the Reviewer
-
I understand the intent of this MR -
All automated tests pass -
Up-to-date CHANGELOG.md (or not necessary) -
Appropriate user and developer documentation (or not necessary) -
The test environment setup works and the intended behavior is reproducible in the test environment -
In-code documentation and comments are up-to-date. -
Check: Are there specifications? Are they satisfied?
Edited by Florian Spreckelsen
Merge request reports
Activity
assigned to @i.nueske
mentioned in issue #240 (closed)
- Resolved by Florian Spreckelsen
- Resolved by Florian Spreckelsen
- Resolved by Florian Spreckelsen
- Resolved by Florian Spreckelsen
777 778 if self._authenticator._credentials_provider is None: 778 779 raise ValueError( 779 780 "No credentials provider set. Please call configure_connection() first.") 780 781 return self._authenticator._credentials_provider.username mentioned in commit 1faa79e7
Please register or sign in to reply