Gabriel Gouvine
Gabriel Gouvine
Thanks for looking into this so quickly! It would be nice to have the same check when using the APIs - maybe just making it an error, as I am...
Hi, Thanks for your contribution. Sorry, I've not been active in a while. I'll check with newer GCC and fix this - or if you have a pull request I'll...
@SebastianSchlag Thank you very much for the follow up. That's nice to have!
You can (kind of) do this with the `ll_explore` command already, using `-delay` as an objective and picking a solution with zero additional delay. It's not yet possible from the...
It's likely related to the thread bug on Windows, #1044 and #1639. You can work around it by setting the `threads=1` option
Which version of Pyomo are you using? It looks a lot like [this Pyomo bug](https://github.com/Pyomo/pyomo/issues/1997)
For the error output, I think it is because the log header is written even during calls to addVars or addRows, but only the output of solve() is intercepted by...
You're right, it's not probably not a change to make on Highs' side. Then I think it's a matter of adding the following code around all calls involving self._solver_model in...
> Thanks. I'm still puzzled that we've not had more people reporting this No idea either. Maybe it only happens on Windows? Or everyone saw it and ignored it 😂
I think Highs hanging may still be a Highs issue