You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, this makes debugging challenging since we can't halt execution at a given optimizer failure and makes tracebacks less helpful for end users (maybe not a super common end user need, but would be helpful for bug reports at the very least).
Instead, I propose that we convert any errors into warnings when multiple optimizers are used, which has a few benefits.
warnings can be emitted immediately, so if fits take a long time to run the failure of a fit is communicated earlier
warnings can still be converted into errors using options(warn = 2), which allows an opportunity to get a useful traceback
this would reduce a lot of the complexity of capturing and re-emitting errors
The text was updated successfully, but these errors were encountered:
I noticed recently that we capture and re-emit errors during fit, which seems to be a fail-safe for potential failures using different optimizers.
However, this makes debugging challenging since we can't halt execution at a given optimizer failure and makes tracebacks less helpful for end users (maybe not a super common end user need, but would be helpful for bug reports at the very least).
Instead, I propose that we convert any errors into warnings when multiple optimizers are used, which has a few benefits.
options(warn = 2)
, which allows an opportunity to get a useful tracebackThe text was updated successfully, but these errors were encountered: