id <- orderly2::orderly_run("data")
-## ℹ Starting packet 'data' `20231003-095631-31f74b7d` at 2023-10-03 09:56:31.213849
+## ℹ Starting packet 'data' `20231004-080923-c335c2a5` at 2023-10-04 08:09:23.775285
## > orderly2::orderly_artefact("Final data", "data.rds")
## > saveRDS(mtcars, "data.rds")
## ✔ Finished running orderly.R
-## ℹ Finished 20231003-095631-31f74b7d at 2023-10-03 09:56:31.33207 (0.1182208 secs)
+## ℹ Finished 20231004-080923-c335c2a5 at 2023-10-04 08:09:23.851522 (0.07623744 secs)
Perhaps it takes several goes for Alice to be happy with the analysis, but at some point she has something ready to share. She can then “push” the final packet up onto their server:
@@ -247,18 +247,18 @@Having seen there is a new “data” packet here, he can pull this down locally (TODO: mrc-4414 makes this nicer):
orderly2::orderly_location_pull_packet(id)
## ℹ Looking for suitable files already on disk
## ℹ Need to fetch 2 files (1.3 kB) from 1 location
-## ⠙ Fetching file 1/2 (1.2 kB) from 'server' | ETA: 0s [7ms]
-## ✔ Fetched 2 files (1.3 kB) from 'server' in 43ms.
+## ⠙ Fetching file 1/2 (1.2 kB) from 'server' | ETA: 0s [5ms]
+## ✔ Fetched 2 files (1.3 kB) from 'server' in 31ms.
## Now Bob is in a position to develop against the same packet that -Alice ran (20231003-095631-31f74b7d)
+Alice ran (20231004-080923-c335c2a5)
id1 <- orderly2::orderly_run("data", root = path)
-## ℹ Starting packet 'data' `20231003-095636-088eab7c` at 2023-10-03 09:56:36.039729
+## ℹ Starting packet 'data' `20231004-080927-567483f7` at 2023-10-04 08:09:27.341802
## > d <- read.csv("data.csv")
## > d$z <- resid(lm(y ~ x, d))
## > saveRDS(d, "data.rds")
## ✔ Finished running orderly.R
-## ℹ Finished 20231003-095636-088eab7c at 2023-10-03 09:56:36.114331 (0.07460165 secs)
+## ℹ Finished 20231004-080927-567483f7 at 2023-10-04 08:09:27.386037 (0.04423475 secs)
id2 <- orderly2::orderly_run("analysis", root = path)
-## ℹ Starting packet 'analysis' `20231003-095636-2845066e` at 2023-10-03 09:56:36.163851
+## ℹ Starting packet 'analysis' `20231004-080927-6a143911` at 2023-10-04 08:09:27.418132
## > orderly2::orderly_dependency("data", "latest()", "data.rds")
-## ℹ Depending on data @ `20231003-095636-088eab7c` (via latest(name == "data"))
+## ℹ Depending on data @ `20231004-080927-567483f7` (via latest(name == "data"))
## > d <- readRDS("data.rds")
## > png("analysis.png")
## > plot(y ~ x, d)
@@ -170,14 +170,14 @@ Basic use## agg_png
## 2
## ✔ Finished running orderly.R
-## ℹ Finished 20231003-095636-2845066e at 2023-10-03 09:56:36.327224 (0.1633728 secs)
When we look at the metadata for the packet created from the
analysis report, we can see it has used
-20231003-095636-088eab7c as its dependency:
20231004-080927-567483f7 as its dependency:
orderly2::orderly_metadata(id2, root = path)$depends
## packet query files
-## 1 20231003-095636-088eab7c latest(name == "data") data.rds....(indeed it had to, there is only one copy of the data
packet to pick from).
cyl:
orderly2::orderly_run("data", list(cyl = 4), root = path)
-## ℹ Starting packet 'data' `20231003-095636-e03744a4` at 2023-10-03 09:56:36.881973
+## ℹ Starting packet 'data' `20231004-080928-073db51f` at 2023-10-04 08:09:28.032516
## ℹ Parameters:
## • cyl: 4
## > orderly2::orderly_parameters(cyl = NULL)
## > d <- mtcars[mtcars$cyl == cyl, ]
## > saveRDS(d, "data.rds")
## ✔ Finished running orderly.R
-## ℹ Finished 20231003-095636-e03744a4 at 2023-10-03 09:56:36.943391 (0.06141782 secs)
-## [1] "20231003-095636-e03744a4"
+## ℹ Finished 20231004-080928-073db51f at 2023-10-04 08:09:28.076217 (0.04370141 secs)
+## [1] "20231004-080928-073db51f"
orderly2::orderly_run("data", list(cyl = 6), root = path)
-## ℹ Starting packet 'data' `20231003-095636-f97b7507` at 2023-10-03 09:56:36.979977
+## ℹ Starting packet 'data' `20231004-080928-19602cb6` at 2023-10-04 08:09:28.103111
## ℹ Parameters:
## • cyl: 6
## > orderly2::orderly_parameters(cyl = NULL)
## > d <- mtcars[mtcars$cyl == cyl, ]
## > saveRDS(d, "data.rds")
## ✔ Finished running orderly.R
-## ℹ Finished 20231003-095636-f97b7507 at 2023-10-03 09:56:37.041861 (0.06188345 secs)
-## [1] "20231003-095636-f97b7507"
+## ℹ Finished 20231004-080928-19602cb6 at 2023-10-04 08:09:28.146066 (0.04295492 secs)
+## [1] "20231004-080928-19602cb6"
orderly2::orderly_run("data", list(cyl = 8), root = path)
-## ℹ Starting packet 'data' `20231003-095637-15244104` at 2023-10-03 09:56:37.088557
+## ℹ Starting packet 'data' `20231004-080928-2cbbb213` at 2023-10-04 08:09:28.178881
## ℹ Parameters:
## • cyl: 8
## > orderly2::orderly_parameters(cyl = NULL)
## > d <- mtcars[mtcars$cyl == cyl, ]
## > saveRDS(d, "data.rds")
## ✔ Finished running orderly.R
-## ℹ Finished 20231003-095637-15244104 at 2023-10-03 09:56:37.140255 (0.05169845 secs)
-## [1] "20231003-095637-15244104"Our follow-on analysis contains:
orderly2::orderly_parameters(cyl = NULL) @@ -248,7 +248,7 @@).Filtering candidates by parametersthis:cyl
+## ℹ Finished 20231004-080928-636b961d at 2023-10-04 08:09:28.463194 (0.07053256 secs) +## [1] "20231004-080928-636b961d"orderly2::orderly_run("analysis", list(cyl = 4), root = path) -## ℹ Starting packet 'analysis' `20231003-095637-5d76d45d` at 2023-10-03 09:56:37.370965 +## ℹ Starting packet 'analysis' `20231004-080928-636b961d` at 2023-10-04 08:09:28.392661 ## ℹ Parameters: ## • cyl: 4 ## > orderly2::orderly_parameters(cyl = NULL) @@ -256,7 +256,7 @@Filtering candidates by parameters## + "data", ## + "latest(parameter:cyl == this:cyl)", ## + "data.rds") -## ℹ Depending on data @ `20231003-095636-e03744a4` (via latest(parameter:cyl == this:cyl && name == "data")) +## ℹ Depending on data @ `20231004-080928-073db51f` (via latest(parameter:cyl == this:cyl && name == "data")) ## > d <- readRDS("data.rds") ## > png("analysis.png") ## > plot(mpg ~ disp, d) @@ -264,8 +264,8 @@
Filtering candidates by parameters## agg_png ## 2 ## ✔ Finished running orderly.R -## ℹ Finished 20231003-095637-5d76d45d at 2023-10-03 09:56:37.464619 (0.09365392 secs) -## [1] "20231003-095637-5d76d45d"
orderly2::orderly_run("analysis", list(cyl = 9000), root = path)
-## ℹ Starting packet 'analysis' `20231003-095637-96e0611e` at 2023-10-03 09:56:37.595574
+## ℹ Starting packet 'analysis' `20231004-080928-8f7af19c` at 2023-10-04 08:09:28.564735
## ℹ Parameters:
## • cyl: 9000
## > orderly2::orderly_parameters(cyl = NULL)
@@ -282,7 +282,7 @@ Interpreting errors## + "latest(parameter:cyl == this:cyl)",
## + "data.rds")
## ✖ Error running orderly.R
-## ℹ Finished 20231003-095637-96e0611e at 2023-10-03 09:56:37.719587 (0.1240129 secs)
+## ℹ Finished 20231004-080928-8f7af19c at 2023-10-04 08:09:28.653859 (0.0891242 secs)
## Error in `orderly2::orderly_run()`:
## ! Failed to run report
## Caused by error in `outpack_packet_use_dependency()`:
@@ -339,8 +339,8 @@ Interpreting errors## [1] 3
##
## $found
-## [1] "20231003-095636-e03744a4" "20231003-095636-f97b7507"
-## [3] "20231003-095637-15244104"
(this would have worked with
rlang::last_error()$explanation$parts$A too).
You can also use orderly2::orderly_metadata_extract to
@@ -351,9 +351,9 @@
cyl took in the evaluating environment.
Instead of a query, you can provide a single id (e.g,
-20231003-095637-5d76d45d), which would mean that even as
+20231004-080928-636b961d), which would mean that even as
new copies of the data packet are created, this dependency
will always resolve to the same value.
You can chain together logical operations with diff --git a/articles/introduction.html b/articles/introduction.html index 96c5e781..3e0519c6 100644 --- a/articles/introduction.html +++ b/articles/introduction.html @@ -113,7 +113,7 @@
path <- tempfile() # we'll use a temporary directory here
orderly2::orderly_init(path)
-## ✔ Created orderly root at '/tmp/RtmpbCbE7C/file1c097c91522b'which creates a few files:
## . ## ├── .outpack @@ -161,14 +161,14 @@:Creating your first orderly reportorderly2::orderly_run()
+## [1] "20231004-080932-6ea60175"id <- orderly2::orderly_run("incoming_data", root = path) -## ℹ Starting packet 'incoming_data' `20231003-095643-0d123dd9` at 2023-10-03 09:56:43.060596 +## ℹ Starting packet 'incoming_data' `20231004-080932-6ea60175` at 2023-10-04 08:09:32.438523 ## > d <- read.csv("data.csv") ## > d$z <- resid(lm(y ~ x, d)) ## > saveRDS(d, "data.rds") ## ✔ Finished running orderly.R -## ℹ Finished 20231003-095643-0d123dd9 at 2023-10-03 09:56:43.186493 (0.1258976 secs) +## ℹ Finished 20231004-080932-6ea60175 at 2023-10-04 08:09:32.519363 (0.08083987 secs) id -## [1] "20231003-095643-0d123dd9"
The id that is created is a new identifier for the
packet that will be both unique among all packets (within reason) and
chronologically sortable. A packet that has an id that sorts after
@@ -177,7 +177,7 @@
## .
## ├── archive
## │ └── incoming_data
-## │ └── 20231003-095643-0d123dd9
+## │ └── 20231004-080932-6ea60175
## │ ├── data.csv
## │ ├── data.rds
## │ └── orderly.R
@@ -190,7 +190,7 @@ Creating your first orderly report## └── orderly.R
A few things have changed here:
orderly2::orderly_run():
id <- orderly2::orderly_run("analysis", root = path)
-## ℹ Starting packet 'analysis' `20231003-095643-d8205607` at 2023-10-03 09:56:43.849989
+## ℹ Starting packet 'analysis' `20231004-080933-05676aac` at 2023-10-04 08:09:33.025157
## > orderly2::orderly_dependency("incoming_data", "latest()",
## + c("incoming.rds" = "data.rds"))
-## ℹ Depending on incoming_data @ `20231003-095643-0d123dd9` (via latest(name == "incoming_data"))
+## ℹ Depending on incoming_data @ `20231004-080932-6ea60175` (via latest(name == "incoming_data"))
## > d <- readRDS("incoming.rds")
## > png("analysis.png")
## > plot(y ~ x, d)
@@ -273,7 +273,7 @@ Depending on packets from anot
## agg_png
## 2
## ✔ Finished running orderly.R
-## ℹ Finished 20231003-095643-d8205607 at 2023-10-03 09:56:44.012722 (0.1627326 secs)
For more information on dependencies, see
vignette("dependencies").
id <- orderly2::orderly_run("incoming_data", root = path)
-## ℹ Starting packet 'incoming_data' `20231003-095644-51a443ba` at 2023-10-03 09:56:44.322373
+## ℹ Starting packet 'incoming_data' `20231004-080933-5eb5c6d2` at 2023-10-04 08:09:33.372579
## > orderly2::orderly_strict_mode()
## > orderly2::orderly_resource("data.csv")
## > orderly2::orderly_artefact("Processed data", "data.rds")
@@ -355,7 +355,7 @@ Available in-report orderly comman
## > d$z <- resid(lm(y ~ x, d))
## > saveRDS(d, "data.rds")
## ✔ Finished running orderly.R
-## ℹ Finished 20231003-095644-51a443ba at 2023-10-03 09:56:44.379609 (0.05723548 secs)
id <- orderly2::orderly_run("random", list(n_samples = 15), root = path)
-## ℹ Starting packet 'random' `20231003-095644-b2e653bb` at 2023-10-03 09:56:44.705062
+## ℹ Starting packet 'random' `20231004-080933-a68db410` at 2023-10-04 08:09:33.654589
## ℹ Parameters:
## • n_samples: 15
## > orderly2::orderly_parameters(n_samples = 10)
@@ -404,7 +404,7 @@ Parameterised reports## > d <- data.frame(x = x, y = x + rnorm(n_samples))
## > saveRDS(d, "data.rds")
## ✔ Finished running orderly.R
-## ℹ Finished 20231003-095644-b2e653bb at 2023-10-03 09:56:44.769163 (0.06410122 secs)
Our resulting file has 15 rows, as the parameter we passed in affected the report:
@@ -412,32 +412,32 @@Parameterised reports dest = dest, root = path) readRDS(file.path(dest, "random.rds")) ## x y -## 1 1 3.192031 -## 2 2 1.513400 -## 3 3 3.200582 -## 4 4 3.614644 -## 5 5 3.842731 -## 6 6 4.432074 -## 7 7 8.416593 -## 8 8 7.417523 -## 9 9 10.017392 -## 10 10 9.591743 -## 11 11 11.225500 -## 12 12 10.815255 -## 13 13 12.761085 -## 14 14 13.862239 -## 15 15 14.882998
You can use these parameters in orderly’s search functions. For example we can find the most recent version of a packet by running:
orderly2::orderly_search('latest(name == "random")',
root = path)
-## [1] "20231003-095644-b2e653bb"But we can also pass in parameter queries here:
orderly2::orderly_search('latest(name == "random" && parameter:n_samples > 10)',
root = path)
-## [1] "20231003-095644-b2e653bb"These can be used within orderly2::orderly_dependency()
(the name == "random" part is implied by the first
name argument), for example
## .
## ├── archive
## │ ├── analysis
-## │ │ └── 20231003-095643-d8205607
+## │ │ └── 20231004-080933-05676aac
## │ │ ├── analysis.png
## │ │ ├── incoming.rds
## │ │ └── orderly.R
## │ ├── incoming_data
-## │ │ ├── 20231003-095643-0d123dd9
+## │ │ ├── 20231004-080932-6ea60175
## │ │ │ ├── data.csv
## │ │ │ ├── data.rds
## │ │ │ └── orderly.R
-## │ │ └── 20231003-095644-51a443ba
+## │ │ └── 20231004-080933-5eb5c6d2
## │ │ ├── data.csv
## │ │ ├── data.rds
## │ │ └── orderly.R
## │ └── random
-## │ └── 20231003-095644-b2e653bb
+## │ └── 20231004-080933-a68db410
## │ ├── data.rds
## │ └── orderly.R
## ├── draft
@@ -514,7 +514,7 @@ Shared resourcesWe can run this:
id <- orderly2::orderly_run("use_shared", root = path)
-## ℹ Starting packet 'use_shared' `20231003-095645-7b8998a2` at 2023-10-03 09:56:45.488799
+## ℹ Starting packet 'use_shared' `20231004-080934-3a67c122` at 2023-10-04 08:09:34.232477
## > orderly2::orderly_shared_resource(data.csv = "data.csv")
## > orderly2::orderly_artefact("analysis", "analysis.png")
## > d <- read.csv("data.csv")
@@ -524,11 +524,11 @@ Shared resources## agg_png
## 2
## ✔ Finished running orderly.R
-## ℹ Finished 20231003-095645-7b8998a2 at 2023-10-03 09:56:45.556732 (0.0679338 secs)
+## ℹ Finished 20231004-080934-3a67c122 at 2023-10-04 08:09:34.279756 (0.04727888 secs)
In the resulting archive, the file that was used from the shared directory is present:
## archive/use_shared
-## └── 20231003-095645-7b8998a2
+## └── 20231004-080934-3a67c122
## ├── analysis.png
## ├── data.csv
## └── orderly.RWhen we run the analysis task, it will pull in the most
-recent version (20231003-095644-51a443ba). However, if you
+recent version (20231004-080933-5eb5c6d2). However, if you
had deleted this manually (e.g., to save space or accidentally) or
corrupted it (e.g., by opening some output in Excel and letting it save
changes) it will not be able to be included, and running
analysis will fail:
orderly2::orderly_run("analysis", root = path)
-## ℹ Starting packet 'analysis' `20231003-095646-6f334b8b` at 2023-10-03 09:56:46.440592
+## ℹ Starting packet 'analysis' `20231004-080934-f55e0d55` at 2023-10-04 08:09:34.962376
## > orderly2::orderly_dependency("incoming_data", "latest()",
## + c("incoming.rds" = "data.rds"))
## ✖ Error running orderly.R
-## ℹ Finished 20231003-095646-6f334b8b at 2023-10-03 09:56:46.608328 (0.1677368 secs)
+## ℹ Finished 20231004-080934-f55e0d55 at 2023-10-04 08:09:35.06874 (0.106364 secs)
## Error in `orderly2::orderly_run()`:
## ! Failed to run report
## Caused by error in `orderly_copy_files()`:
-## ! Unable to copy files, due to deleted packet 20231003-095644-51a443ba
-## ℹ Consider 'orderly2::orderly_validate_archive("20231003-095644-51a443ba",
+## ! Unable to copy files, due to deleted packet 20231004-080933-5eb5c6d2
+## ℹ Consider 'orderly2::orderly_validate_archive("20231004-080933-5eb5c6d2",
## action = "orphan")' to remove this packet from consideration
## Caused by error:
## ! File not found in archive
## ✖ data.rdsThe error here tries to be fairly informative, telling us that we
failed because when copying files from
-20231003-095644-51a443ba we found that the packet was
+20231004-080933-5eb5c6d2 we found that the packet was
corrupt, because the file data.rds was not found in the
archive. It also suggests a fix; we can tell orderly2 that
-20231003-095644-51a443ba is “orphaned” and should not be
+20231004-080933-5eb5c6d2 is “orphaned” and should not be
considered for inclusion when we look for dependencies.
We can carry out the suggestion and just validate this packet by running
-orderly2::orderly_validate_archive("20231003-095644-51a443ba", action = "orphan")orderly2::orderly_validate_archive("20231004-080933-5eb5c6d2", action = "orphan")
or we can validate all the packets we have:
orderly2::orderly_validate_archive(action = "orphan", root = path)
-## ✔ 20231003-095643-0d123dd9 (incoming_data) is valid
-## ✔ 20231003-095643-d8205607 (analysis) is valid
-## ✖ 20231003-095644-51a443ba (incoming_data) is invalid due to its files
-## ✔ 20231003-095644-b2e653bb (random) is valid
-## ✔ 20231003-095645-7b8998a2 (use_shared) is validIf we had the option core.require_complete_tree enabled,
then this process would also look for any packets that used our
now-deleted packet and orphan those too, as we no longer have a complete
@@ -753,16 +753,16 @@
As can be perhaps inferred from the filenames, the files
.outpack/metadata/<packet-id> are the metadata for
each packet as it has been run. The files
@@ -783,35 +783,35 @@
The files under .outpack/files/ should never be modified
or deleted. This approach to storage naturally deduplicates the file
archive, so that a large file used in many places is only ever stored
diff --git a/articles/plugins.html b/articles/plugins.html
index a8bc0908..728c110e 100644
--- a/articles/plugins.html
+++ b/articles/plugins.html
@@ -151,7 +151,7 @@
minimum_orderly_version: 1.99.0
plugins:
example.db:
- path: /tmp/RtmpOl8VEQ/file1cf8593f0403Our plugin is called example.db and is listed within the
plugins section, along with its configuration; in this case
indicating the path where the SQLite file can be loaded from.
orderly2::orderly_run("example", root = path_root)
-## ℹ Starting packet 'example' `20231003-095700-eeb77169` at 2023-10-03 09:57:00.941672
+## ℹ Starting packet 'example' `20231004-080944-f8302338` at 2023-10-04 08:09:44.975307
## > example.db::query(sql = "SELECT * FROM mtcars WHERE cyl == 4", as = "dat")
## > orderly2::orderly_artefact("Summary of data", "data.rds")
## > saveRDS(summary(dat), "data.rds")
## ✔ Finished running orderly.R
-## ℹ Finished 20231003-095700-eeb77169 at 2023-10-03 09:57:01.138326 (0.1966538 secs)
-## [1] "20231003-095700-eeb77169"
+## ℹ Finished 20231004-080944-f8302338 at 2023-10-04 08:09:45.096372 (0.1210651 secs)
+## [1] "20231004-080944-f8302338"
## .
## ├── archive
## │ └── example
-## │ └── 20231003-095700-eeb77169
+## │ └── 20231004-080944-f8302338
## │ ├── data.rds
## │ └── orderly.R
## ├── draft
diff --git a/articles/troubleshooting.html b/articles/troubleshooting.html
index dabc9f85..c1028d04 100644
--- a/articles/troubleshooting.html
+++ b/articles/troubleshooting.html
@@ -130,21 +130,21 @@ Outpack files accidentally
## <https://mrc-ide.github.io/orderly2/articles/troubleshooting.html>
## This warning is displayed once per session.
## ✔ Wrote '.gitignore'## ℹ Starting packet 'data' `20231003-095712-edf65b8b` at 2023-10-03 09:57:12.935178## ℹ Starting packet 'data' `20231004-080953-aafa583e` at 2023-10-04 08:09:53.671788## > orderly2::orderly_artefact("Final data", "data.rds")
## > saveRDS(mtcars, "data.rds")## ✔ Finished running orderly.R## ℹ Finished 20231003-095712-edf65b8b at 2023-10-03 09:57:13.007963 (0.07278538 secs)## [1] "20231003-095712-edf65b8b"## ℹ Finished 20231004-080953-aafa583e at 2023-10-04 08:09:53.715145 (0.04335666 secs)## [1] "20231004-080953-aafa583e"subsequent calls will not display the warning:
orderly2::orderly_run("data", root = path)## ℹ Starting packet 'data' `20231003-095713-239607a7` at 2023-10-03 09:57:13.144902## ℹ Starting packet 'data' `20231004-080953-d062eef2` at 2023-10-04 08:09:53.817879## > orderly2::orderly_artefact("Final data", "data.rds")
## > saveRDS(mtcars, "data.rds")## ✔ Finished running orderly.R## ℹ Finished 20231003-095713-239607a7 at 2023-10-03 09:57:13.187819 (0.04291749 secs)## [1] "20231003-095713-239607a7"## ℹ Finished 20231004-080953-d062eef2 at 2023-10-04 08:09:53.845932 (0.02805305 secs)## [1] "20231004-080953-d062eef2"The rest of this section discusses how you might permanently fix the issue.
# Create a simple example:
path <- orderly2::orderly_example("default")
-#> ✔ Created orderly root at '/tmp/RtmpGmeMVK/file188c2b15692'
+#> ✔ Created orderly root at '/tmp/RtmpFKr3bd/file18d232daf8ba'
# We simulate running a packet interactively by using 'source';
# you might have run this line-by-line, or with the "Source"
# button in Rstudio.
source(file.path(path, "src/data/orderly.R"), chdir = TRUE)
-#> Warning: cannot open file '/tmp/RtmpGmeMVK/file188c2b15692/src/data/orderly.R': No such file or directory
+#> Warning: cannot open file '/tmp/RtmpFKr3bd/file18d232daf8ba/src/data/orderly.R': No such file or directory
#> Error in file(filename, "r", encoding = encoding): cannot open the connection
# Having run this, the output of the report is present in the
# source directory:
fs::dir_tree(path)
-#> Error: [ENOENT] Failed to search directory '/tmp/RtmpGmeMVK/file188c2b15692': no such file or directory
+#> Error: [ENOENT] Failed to search directory '/tmp/RtmpFKr3bd/file18d232daf8ba': no such file or directory
# We can detect what might want cleaning up by running
# "orderly_cleanup_status":
orderly2::orderly_cleanup_status("data", root = path)
-#> Error: Directory does not exist: '/tmp/RtmpGmeMVK/file188c2b15692'
+#> Error: Directory does not exist: '/tmp/RtmpFKr3bd/file18d232daf8ba'
# Soon this will print more nicely to the screen, but for now you
# can see that the status of "data.rds" is "derived", which means
@@ -176,7 +176,7 @@ Examples
# Do the actual deletion:
orderly2::orderly_cleanup("data", root = path)
-#> Error: Directory does not exist: '/tmp/RtmpGmeMVK/file188c2b15692'
+#> Error: Directory does not exist: '/tmp/RtmpFKr3bd/file18d232daf8ba'