You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let's say we have the following hierarchy, where data/bar and data/foo are individual outputs.
When you do dvc push data, dvc does not know to search for outputs inside the path.
.└── data ├── bar └── foo
At the moment, target only supports filtering subpath of an output or an exact path to the output.
So, it would work for data/foo or data/bar. And, if the data was being tracked as single output, data/bar and data/foo will work to filter the data output.
Regarding implementation, we have internal utilities to collect all outputs of a path using find_outs_by_path(recursive=True). But since it can return multiple stages, there may be assumptions that it can return only a single output/stage which have to be fixed. And, more importantly, test that it does not affect other commands, since this collect_granular is used in a lot of places.
Let's say we have the following hierarchy, where
data/bar
anddata/foo
are individual outputs.When you do
dvc push data
, dvc does not know to search for outputs inside the path.At the moment,
target
only supports filtering subpath of an output or an exact path to the output.So, it would work for
data/foo
ordata/bar
. And, if thedata
was being tracked as single output,data/bar
anddata/foo
will work to filter thedata
output.Regarding implementation, we have internal utilities to collect all outputs of a path using
find_outs_by_path(recursive=True)
. But since it can return multiple stages, there may be assumptions that it can return only a single output/stage which have to be fixed. And, more importantly, test that it does not affect other commands, since thiscollect_granular
is used in a lot of places.dvc/dvc/repo/stage.py
Line 396 in 44b78b8
Related: #10203.
The text was updated successfully, but these errors were encountered: