Oscar Dowson

You need to follow the second half of my previous comment.

You can make a PR to improve the documentation by clicking on the pencil Icon at the top of the README on the homepage: https://github.com/JuliaOpt/NLopt.jl/edit/master/README.md

Please provide a reproducible example.

This was a massive failure. It fails immediately: ```Julia julia> alpine = MOI.OptimizerWithAttributes( Alpine.Optimizer, "nlp_solver" => IPOPT, "mip_solver" => CBC, ) MathOptInterface.OptimizerWithAttributes(Alpine.Optimizer, Pair{MathOptInterface.AbstractOptimizerAttribute, Any}[MathOptInterface.RawOptimizerAttribute("nlp_solver") => MathOptInterface.OptimizerWithAttributes(Ipopt.Optimizer, Pair{MathOptInterface.AbstractOptimizerAttribute, Any}[MathOptInterface.Silent() => true,...

Yeah I don't know if you want Juniper to act as if `SLOW_PROGRESS` is the same as optimal. It's really telling you that there is a problem with the model...

This had the same underlying issue as https://github.com/lanl-ansi/Juniper.jl/pull/250. Now it should be fine because Juniper can return `SLOW_PROGRESS` as the termination status, and `RESULT_STATUS_UNKNOWN` for the primal status. Claiming that...

The main difference is that we don't have a solution type. Solutions are stored inside the model object which is owned by each package/solution algorithm (e.g, `Cbc.Optimizer`, `Optim.Optimizer`, ...). Then...

Can reproduce this on `Optimization#master`.

It's related to passing `ref` as the parameter argument. If I omit that, it works. @ccoffin, I'll update that branch you have going. You can trigger a weird error by...

Leaving a bread-crumb to https://jump.dev/JuMP.jl/stable/manual/callbacks/, which contains the documentation of the callbacks JuMP supports. However I think a good rule of thumb is "if in doubt, follow Gurobi."