Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

run: add --outs-persist and --outs-persist-no-cache description #217

Closed
wants to merge 3 commits into from

Conversation

pared
Copy link
Contributor

@pared pared commented Mar 25, 2019

Related to #1214

@pared pared requested review from shcheklein and robogeek March 25, 2019 15:47
@@ -84,6 +84,17 @@ automatically under DVC control. In case of metrics it's pretty usual because
metric files are small enough to be put into Git or other underlying version
control system. See also the difference between `-o` and `-O` options.

* `--outs-persist` - the same as `-o` except outputs will not be removed in case
of [`dvc repro`](https://dvc.org/doc/commands-reference/repro#repro) command.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please, keep the same indent as in the options around

* `--outs-persist` - the same as `-o` except outputs will not be removed in case
of [`dvc repro`](https://dvc.org/doc/commands-reference/repro#repro) command.
Upon running [`dvc repro`](https://dvc.org/doc/commands-reference/repro#repro),
In case of `-o` target file is removed (if exists) before performing command
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

target file is confusing (sounds more like DVC file itself in this context). Why don't we specify that in case of -o or -O data files or directories produced in the previous run are removed ... or something like this

Copy link
Member

@shcheklein shcheklein left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

Put some comments to improve/fix the doc.

Also:

  1. Mention where these options are useful. One-two sentence if we can get the from the user request.
  2. Mention that these options are safe and take care about unprotecting files and that it might affect the performance with certain cache settings (cache=hardlink,symlink?)
  3. Example - let's not use foo, bar names. Let's come up with something more meaningful. It's hard to understand what's going on when input file is bar and output is foo.

@pared pared requested a review from shcheklein March 26, 2019 13:04
cache types (symlink, hardlink) reproduction step will be prolonged by time
necessary to create copies. `--outs-persist` might still overwrite existing
outputs if `run` command somehow removes existing output (example in
[Examples](#Examples)).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❤️ I would remove (example in Examples) though


* Difference between `run --outs` and `run --outs-persist`.
This example shows how using `--outs-persist` influences
reproduction step.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can fit into one line?

@pared pared requested a review from shcheklein March 26, 2019 20:30
@pared
Copy link
Contributor Author

pared commented Nov 27, 2019

@shcheklein can we close it for now?

@shcheklein
Copy link
Member

@pared agreed!

@shcheklein shcheklein closed this Nov 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants