targets
tries to avoid running two concurrent instances
of tar_make()
on the same pipeline writing to the same data store.
Sometimes it generates false positives (meaning tar_make()
throws
this error even though there is only one instance of the pipeline
running.) If there is a false positive, tar_unblock_process()
gets the pipeline unstuck by removing the _targets/meta/process
file.
This allows the next call to tar_make()
to resume.
Usage
tar_unblock_process(store = targets::tar_config_get("store"))
See also
Other utilities:
tar_active()
,
tar_backoff()
,
tar_call()
,
tar_cancel()
,
tar_definition()
,
tar_described_as()
,
tar_envir()
,
tar_format_get()
,
tar_group()
,
tar_name()
,
tar_path()
,
tar_path_script()
,
tar_path_script_support()
,
tar_path_store()
,
tar_path_target()
,
tar_source()
,
tar_store()