Paul Goulart

Alternative suggestion : in your example, use: ``` qsp.solve(verbose=True, solver=cp.CLARABEL) ``` which uses an interior point method instead. That solver is always deterministic and will also give higher accuracy solutions.

I think you might be better served by instead setting `adaptive_rho_interval` to some positive integer, say 25 or 50, and keeping `adaptive_rho = true`. That would allow the solver to...

This appears to be fixed by #114

We have implemented a feature that will automatically eliminate constraints with very large bounds, which I think means that that the issue described here is no longer relevant. This is...

A fix for this is still pending, but will be much easier upon resolution of : https://github.com/JuliaSparse/SparseArrays.jl/issues/275 Fixed for pardiso in #114

That error indicates that q is a null pointer. Are you sure that the q you are passing is properly initialized?

Fixed in #114. Thank you for reporting this error, since it exposed a fairly unusual edge case.

Out of memory errors and complaint about matrix ordering are also symptomatic of the problems in #73 and #88. It could be that the error is caused by a 32bit...

If I replace `JuMP` with `MKLSparse` (the cause of the issue in #73) then I see similar behaviour. Including `MKLSparse` first produces a crash but the other way around does...

I will look into it and see what I can find. It's pretty clear that there is a type error of some kind when making a `ccall` to the pardiso...