-
Notifications
You must be signed in to change notification settings - Fork 141
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 bug in max-cut solver (issue #611) #635
Conversation
Hi @t-imamichi, @woodsp-ibm, @stefan-woerner! |
Pull Request Test Coverage Report for Build 11496393782Details
💛 - Coveralls |
Thank you for fixing an issue.
Line 313 in 807d481
https://pylint.pycqa.org/en/latest/user_guide/messages/refactor/too-many-positional-arguments.html |
Let me try the config #637 |
|
I closed #637 following @woodsp-ibm's comment. |
LGTM overall. I wrote some comments. |
c15fe75
to
c72f84c
Compare
d0a336f
to
c72f84c
Compare
11bc552
to
29a679f
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.
LGTM
* fix bug in max-cut solver (issue #611) * fix copyrights * add unknown-option-value as an error message to be ignored by pylint * disable pylint too-many-positional-arguments error for the lines it pops up * fix copyrights * fix max-cut bug (cherry picked from commit 8a7e09e) Co-authored-by: Apostolos Chalkis <[email protected]>
This PR fixes the bug in the max-cut solver as reported in #611