Dave Berenbaum
Dave Berenbaum
> So the idea (as i get it and agree on) on **verify** is do skip the step of dvc pulling as it takes a long time. Yup, sorry if...
We haven't documented the behavior yet, but with the latest release, you should be able to use the `--allow-missing` flag from #9437 (thanks @daavoo) to cover most of this functionality....
It seems the primary blocker here is UI. Let's make a decision so we could move forward. How about `dvc gc --not-in-remote`?
Update on current behavior. I tested with two local remotes, `default` and `other`, and two files, `foo` and `bar`, with `bar.dvc` including `remote: other`: ```bash $ tree . ├── bar.dvc...
Closing as stale. Let's open more specific follow-ups as needed.
Related/duplicate from #9430: > With the addition of virtual operations and `dvc repro --pull`, it's becoming more useful to work without pulling all the data, but `dvc data status` gets...
Related to #8354 and #8409. DVC shouldn't be modifying `version_id` for unchanged files.
@daavoo Since you recently updated these options, do you recall if these issues still exist?
Closing since checkpoints have been deprecated. For discussion about resuming experiments, see https://github.com/iterative/dvclive/issues/505.
@shcheklein @mattseddon What is the default number of commits in VS Code now? Maybe we can make it consistent between both products by defaulting to the same in CLI?