Oscar Dowson

@eminyouskn I invited you to https://github.com/jump-dev/Knitro_jll.jl. It's currently private, but it's an example of what the code would be. We'd change https://github.com/jump-dev/Knitro_jll.jl/blob/main/Artifacts.toml with the proper URLs (currently, they're in my...

There's also a question of whether you want it to be `KNITRO_jll` or `Knitro_jll`. Early history was Knitro.jl, but it got renamed in https://github.com/jump-dev/KNITRO.jl/commit/bf1a59dd4faef0da6302bd8e2bfaf0d173a9380b to KNITRO.jl to match the name...

I think the correct solution to this is to use a license manager: ```Julia using JuMP, KNITRO manager = KNITRO.LMcontext() model = Model(() -> KNITRO.Optimizer(; license_manager = manager)) # maybe...

https://github.com/jump-dev/SumOfSquares.jl/blob/a668a7cc489002f082a8de252c09f761da84836e/src/Certificate/Symmetry/wedderburn.jl#L166-L167

I am strongly against adding this. I want JuliaHub to fix this on their end. I don't want the open-source community to have to do work to make their product...

> I'm not quite sure why this is so controversial, or where > Is coming from. Unless it's just the rhetorical prelude to Yes, all of this. > But at...

I can't comment on the implementation (I don't know Python well), other than to say that, at minimum, this needs a bunch of tests.

I think this is expected. We don't try to compress the non-zero terms, even in trivial cases. Is there any evidence that this is a performance concern?

As a trivial example, a problem with one variable can have > 1 element in the Hessian: ```Julia julia> using JuMP, Ipopt julia> model = Model(Ipopt.Optimizer) A JuMP Model Feasibility...

Do you have an example?