Wouter Bles

Also faced the issue where none of my monitors (internal + external) were detected in v1.13.11. Just installed the v1.14.0-preview-4 you provided above, and everything is working again!

Any reason why this issue was closed? I am also facing these problems and I think adding a sleep() and retry in this package would be a great addition.

I'll see what I can do! I wasn't able to catch the error on application level so I started looking at this package. The change I posted in the other...

Does the repo you suggest also support the https://github.com/gliterd/flysystem-backblaze and https://github.com/gliterd/laravel-backblaze-b2 that depend on this SDK? After taking a quick look at the code I think it would not be...

@rodolfoberrios Dit you not have the issue I described in https://github.com/obregonco/backblaze-b2/issues/2?

It is already possible to use other solvers, I should probably update the docs/readme to reflect that. Any solver that is supported by Pyomo should work. I have personally only...

From the error this looks like an issue with the Pyomo solver interface, not direclty an issue with PyAUGMECON. Could you try to use Pyomo directly (so without pyaugmecon) with...

Interesting indeed. I have mainly been running the 3kp40/3kp50 cases. Which are in the `tests` folder. Did some tests with both versions of the queueing. By the way, make sure...

@yvanoers created a fix for this issue in the latest PR, this bug was introduced by a refactor a while ago. Thanks for discovering the issue! Instead of queuing each...

That's definetely something to look into. I think it might make sense to reset the jump counter when taking a new block of work.