Peter Rowlands (변기호)

still bisecting, but it looks like this bug was introduced in 2.11.0 Using `git checkout ` from example-get-started runs: 2.10.2 ``` example-get-started git:e5e08a2 py:example-get-started ❯ git ls-files .dvc/.gitignore .dvc/config .dvc/plots/confusion.json...

Bug was introduced with https://github.com/iterative/dvc/pull/7712 When we reproduce the exp pipeline, we ensure that all deps and outputs are tracked in either DVC or git. So the end result is...

I can reproduce it, the issue here is that the demo stage dependency is ``` deps: - data/MNIST ``` but the DVC (data) output is `data/MNIST/raw`, so we still end...

You have `artifacts/data` listed as both a dependency and an output in that stage, which is not supported in DVC (due to being a cyclic/circular dependency)

Do we even need the `istextfile` validation for metrics at all? If users are explicitly listing something as a `metrics` stage output, it seems like we should just assume that...

I think this is mostly a duplicate of https://github.com/iterative/dvc/issues/5846

The use case for `dvc run` is for a when a user wants to generate or modify a stage in `dvc.yaml`. This is redundant and confusing, which is why removing/deprecating...

probably related to https://github.com/iterative/dvc/issues/6930 (untracked files being removed on post-run apply)

Applying the merge on the workspace isn't the correct behavior, that would put `-S` modified params into the workspace and not the original params file. I think the fix for...

For the record, metrics collection is now done via the unified repo collection behavior, which should properly handle the repo tree and recursively collect all metrics (when the appropriate CLI...