-
-
Notifications
You must be signed in to change notification settings - Fork 25.9k
WIP #10598 <enet_path does not pass params to coordinate descent solver>(Updated) #10622
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
you need to add a test. I would start with the test by trying to pass a non valid keyword. |
Please put "resolves #xxx" in pr description, not title. Ping once you have test for a review |
Just tested the code.
returns
while adding any valid arguments to the code makes it run smoothly. That being said, I still don't get why my code doesn't pass all the tests on Github's build tests. It compiles |
A test needs to be a piece of code in the corresponding tests directory that successfully runs only if your change is working. Also, this should match other unexpected keyword argument errors, and should be a TypeError rather than a ValueError |
The code works for enet_path (and when I manually put in invalid and valid function arguments), but when running it against test_enet_path, an error pops up saying |
Could you provide a fully reproducible code snippet and the traceback for that error? |
Operating System: Windows 10 Error: So the error pops up when I replace I think it's because the I dug into the files indicated in the traceback, and the second line below seemed to raise the error:
How to reproduce:
Code used:
Traceback:
|
I'll close in favor of #19391. |
Updated the code, sorry for putting in lackluster pull requests. Will put in more attention to detail, something silly like putting in commands after the function ended was easy to prevent.
Reference Issues/PRs
What does this implement/fix? Explain your changes.
Resolves #10598
Any other comments?