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
what action, if any, should the error handler take notify p of the abort and that the progress bar can be disposed rather than getting calls to p() all the way to 100%?
I'm not seeing that progressr has an API for this so I'm wondering if perhaps the design is that callers should do
with_progress({ tryCatch({ ... }, { ... }) })
with progressr disposing when the with_progress block returns regardless of the number calls of p() which might have been missed due to an error occurring? Class progressor has only length and print methods so it doesn't appear possible or for callers to query it for the number of times to call p() to reach completion (not that completion particularly makes much sense an error condition).
Asking because I've got long running future_map()s calling numerical optimization methods that sometimes fail and occasionally future gets hung up when a worker errors and has to be reset. This not uncommonly yields a bunch of complaints from progressr about incomplete progressors.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Couldn't find this in the docs, previous discussions, or issues. Given code like
what action, if any, should the error handler take notify
pof the abort and that the progress bar can be disposed rather than getting calls top()all the way to 100%?I'm not seeing that progressr has an API for this so I'm wondering if perhaps the design is that callers should do
with_progress({ tryCatch({ ... }, { ... }) })with progressr disposing when the
with_progressblock returns regardless of the number calls ofp()which might have been missed due to an error occurring? Class progressor has only length and print methods so it doesn't appear possible or for callers to query it for the number of times to callp()to reach completion (not that completion particularly makes much sense an error condition).Asking because I've got long running
future_map()s calling numerical optimization methods that sometimes fail and occasionally future gets hung up when a worker errors and has to be reset. This not uncommonly yields a bunch of complaints from progressr about incomplete progressors.Beta Was this translation helpful? Give feedback.
All reactions