-
-
Notifications
You must be signed in to change notification settings - Fork 86
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
Update to MathOptInterface v1.0 #218
Conversation
We need to fix this by moving to subpackages. Requires.jl indeed does not play nicely with compatibilities. |
Ah. This is going to need the Nonconvex packages updated. cc @mohamed82008 |
Let's hold off merging this for a bit. I'm looking into a bug that @ccoffrin found. |
Now blocked by: |
@blegat and @jonasmac16 if you want to take a look. |
@odow, looks like Tulip issue was resolved. Is this branch passing tests now? |
I give up. There are still a bunch of compatibility issues with the Nonconvex stuff. If we want to test a bunch of different packages like this, it should be done in separate projects. There's no need to attempt to install everything in a single environment. And the tests don't even pass on |
FWIW, |
@mohamed82008 would you be able to help out with the version issues? |
Let's wait a couple of days and see if we can get some help to get the version conflicts resolved, otherwise we'll go ahead and merge this as is, hope that's ok? |
We plan to split the wrappers out to separate subpackages, like how KernelAbstractions.jl is done with the Our first experiment with doing this is NeuralPDELogging.jl JuliaRegistries/General#57196. It seems like that's working now, so we should do this here. |
I'm just going to merge so I can do a follow-up PR that splits to version controlled subpackages and fix this madness. |
This madness is one of the motivations behind the Nonconvex.jl design of a shell package that loads algorithms from their respective packages. |
Sorry, I didn't have time to look at the PR (in the last 2 weeks of my PhD atm :( ). Happy to help with the subpackages once that is done as this has been on my todo list for some time. |
Note that we moved everything to a subpackage form, so now all of the solvers track their own dependencies in their Project.toml. We need to figure out what's going on with Nonconvex.jl's bindings, but all of the other ones should be good now. |
How does requires work if the requires package introduces breaking changes? I found: JuliaPackaging/Requires.jl#82
It seems like GalacticOptim has some strong compatibility issue with MathOptInterface, and yet there's nothing in the Project.toml to prevent someone installing incompatible versions.
Closes #214
Closes #167