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
Before running custom storage code saved in the data store by tar_format() or tar_repository_cas(), tar_read(), tar_load(), and tar_workspace() now ask whether you trust the data store. Unless the TAR_ASK environment variable is "false", they show a menu in interactive sessions and throw an informative error in non-interactive ones. They never ask inside a running pipeline or during R CMD check. Non-interactive scripts that read custom-format or CAS targets from outside the pipeline now need TAR_ASK = "false". See the new "Trusting custom storage code" section of ?tar_format (#1602).
Query file information only for targets whose data are in _targets/objects/ and which the current pipeline uses: its stems and the current branches of its patterns. Previously, tar_make(), tar_outdated() and friends queried every local target ever recorded in the metadata, including removed targets, superseded branches, targets outside the names selection, and file and URL targets stored elsewhere (#1597, @koefoeden).
Speed up tar_manifest() in large pipelines: build each column in one pass over the targets instead of binding a one-row tibble per target, and compute only the requested fields (#1598, @koefoeden).
Harmonize internal lists of possible values for the error, memory, deployment, storage, and retrieval options (#1587, @koefoeden).
Use label_length instead of label_width to set the maximum number of content characters in visualization node labels (tar_visnetwork(), tar_mermaid(), tar_glimpse(), tar_config_set(), tar_config_get()). label_width still controls the width, but long strings wrap over multiple lines (#1588, @jesse-ross).