Dave Berenbaum

Comments from https://github.com/iterative/dvc/issues/4871: > Currently the `--pull` flag have no impact when used together with the `--downstream` flag. When working in a new repo, one must pull manually all the...

Comment from #4870: > Let's say there is a 3 stages workflow: A -> B -> C: > > * A run `a.py` and produce `a.json`, > > * B...

Another request in discord: https://discord.com/channels/485586884165107732/485596304961962003/945713992825991188 As noted there, this is really important for remote execution, so I think we need to prioritize this soon. cc @pmrowla @karajan1001

In the initial comment for this issue, there is a good summary: "pull whatever is missing and necessary for this repro." I think it's related to https://github.com/iterative/dvc/issues/5369, and that may...

> Determining whether or not the upstream stages are modified requires on having the dependencies available (to see whether or not they have changed) I would like to have an...

@francesco086 You mentioned wanting to have the ability to pull a single stage's dependencies in `dvc pull`. I think we could have this as a related but separate feature request...

> What happens if it's just a regular output that is missing in the workspace? Also an error? Yes. I agree that it's not critical to address this, and it...

A concise summary of the request is to decouple checkpoints from the pipeline. Checkpoints should only be responsible for caching data and generating a Git ref, not any pipeline execution.

@maxagin It's possible that columns change between commits. However, this is also possible within a single commit. We show all columns from all experiments and commits in that case. We...

> * `exp run`: specify an experiment name first time but not when resuming One minor note: You should be able to use `dvc exp run -n $EXP_NAME` even when...