Changelog
Source:NEWS.md
Version 0.10.1
CRAN release: 2025-07-10
Bug Fix
If a mirai future that was terminated abruptly (e.g. via
tools::pskill()or by the operating system), then it was not detected as such. Instead it resulted in an unexpected error that could not be recovered from. Now it is detected and aFutureInterruptErroris signaled, which can then be handled and the future may bereset().result()on an interrupted mirai future would only throw FutureInterruptError the first time. Succeeding calls would result in other errors.resolved()on a mirai future already known to be interrupted would requery the mirai object, instead of returning TRUE immediately.
Version 0.10.0
CRAN release: 2025-06-05
New Features
Now ‘mirai’ futures can be canceled using
cancel(), which also interrupts them by default, which in turn frees up compute resources sooner. Map-reduce API such as future.apply, doFuture, and furrr can take advantage of this by canceling all non-resolved futures whenever they detect an error in one of the futures. Also, canceled futures can bereset()and thereafter relaunched, possibly on another future backend.Now ‘mirai_multisession’ futures relay
immediateCondition:s in near real-time, e.g.progressionconditions signals by the progressr package.
Version 0.2.2
CRAN release: 2024-07-03
Miscellaneous
- Internal updates for mirai (>= 1.1.0), e.g.
mirai::daemons()argumentresilienceis being removed.
Version 0.2.1
CRAN release: 2024-05-15
Bug Fix
-
nbrOfWorkers()andnbrOfFreeWorkers()did not handle mirai dispatcher errors. Because those are integers, these functions would return the error integer value instead of giving aFutureError.