Improve exception-handling in SacessOptimizer #1512
Assignees
Labels
optimization
Related to optimization process
Comments
dweindl
added a commit
to dweindl/pyPESTO
that referenced
this issue
Nov 25, 2024
Previously, uncaught exceptions in SacessOptimizer worker processes would have resulted in deadlocks in `SacessOptimizer.minimize`. These changes will (in most cases) prevent deadlocks and other errors due to missing results from individual workers. Furthermore, this will lead to termination of minimize() relatively soon after an error occurred on some worker - not only after some other exit criterion is met. Closes ICB-DCM#1512.
dweindl
added a commit
to dweindl/pyPESTO
that referenced
this issue
Nov 25, 2024
Previously, uncaught exceptions in SacessOptimizer worker processes would have resulted in deadlocks in `SacessOptimizer.minimize`. These changes will (in most cases) prevent deadlocks and other errors due to missing results from individual workers. Furthermore, this will lead to termination of minimize() relatively soon after an error occurred on some worker - not only after some other exit criterion is met. Closes ICB-DCM#1512.
github-merge-queue bot
pushed a commit
that referenced
this issue
Nov 27, 2024
Previously, uncaught exceptions in SacessOptimizer worker processes would have resulted in deadlocks in `SacessOptimizer.minimize`. These changes will (in most cases) prevent deadlocks and other errors due to missing results from individual workers. Furthermore, this will lead to termination of minimize() relatively soon after an error occurred on some worker - not only after some other exit criterion is met. Closes #1512.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, uncaught exceptions in
SacessWorkers will result in deadlocks inSacessOptimizer.minimize. This needs to change.The text was updated successfully, but these errors were encountered: