The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.
raveio from templatesrs_job considers
Positron-IDEdistill for default report style, if
availableSVG plots to allow image overlaysbase64URI; using base64enc for more
general base64 converterlapply_jobs callback fail to run due
to zero-length messagesstart_job uses callr for maximized
consistency by default@unmarshal, the package is loaded by
defaultwith_rave_parallel with one worker no longer runs in
background, though users can force enabling thisRAVESerializable objects, allowing
comparisons of two R6 objects inheriting this classRAVEFileArray to wrap against
FileArray, allowing file-arrays to be serialized faster
when running with mirailapply_jobs, allowing down-stream packages to use
it for looping with similar behaviors to lapply, while
giving users options to parallel computing the results with
with_rave_parallelRAVESerializable class for mirai,
allowing for fast serialization when running
lapply_jobscat2 is no longer used as logging system and used
logger insteadrave_progress to replace dipsaus;
removed dependencies on dipsauslogger from ravedash so this
function can be used by ravecore and other depending
packagesmirai as the optional background engine to run
jobsRAVE_PIPELINE_ACTIVE
environment set to "true" to allow fast compile and
debuggingpipeline$read once disabled by targets
during evaluation can now runs again with hacksstart_job to start background jobs, which can be
converted into promisestargets version
1.11.1 where use-after-free of cli progress
crashes the pipeline run, the newer versions of that package has fixed
it tooraveio
callsyaml format now sort native lists with
sorted=TRUEcall_pkg_fun for rstudioapi and
use the package functions directly to avoid messing up with
sys.call()entraceThese binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.