Casper da Costa-Luis
Casper da Costa-Luis
Related: `fds` https://dagshub.com/blog/fds-fast-data-science-with-git-and-dvc/
@shcheklein I agree
@dtrifiro from [this](https://github.com/iterative/dvc/issues/7866#issuecomment-1150986716) I understand you prefer `repro` over `run` and would like to (soft)deprecate the latter. In that case, isn't `dvc stage {add,list,repro}` still less confusing than the current...
It's not clear to me that #5846 is a solution. I'm asking about use cases rather than implementation/adding-even-more-confusingly-named-options. A) What are the underlying concepts? afaik it's: 1. Pipelines + makefile-like...
So for clarification we want to support: A) 1. pipelines - create/read/update/delete stages - basic DAG check - advanced DAG check - gnumake-like traverse DAG & run outdated stages -...
> and a better component to display files/bytes at the same time (does `tqdm` support that?). what do you mean? as in show both `files/s` and `bytes/s` simultaneously but have...
(self-requesting review for verifying spec)
`apt update` is usually not recommended inside docker containers (these transient errors is one reason). I wonder if we should follow https://askubuntu.com/questions/65245/apt-get-update-only-for-a-specific-repository
yes but not `apt update` from all lists, right?
We only need to update from the repos we add (ppa, DVC deb), not the ubuntu ones. i.e. https://github.com/iterative/cml/issues/873#issuecomment-1013815690