-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
list . : inconsistent behaviour #5866
Comments
@mattseddon Is this still an issue for you? |
Will come back to you shortly, sorry for the delay. Been caught up away from anything that use |
@dberenbaum the inconsistency is still there but this is not a priority for me (version 2.1.0). QQ what is the best thing to do when I find something that is inconsistent / doesn't make sense but that I don't necessarily need fixed straight away? |
Closing in favor of #5712 |
Good question. I would say just explain the priority for you in the issue whether it is urgent or not. |
Bug Report
Description
Inconsistent behaviour for
dvc list . --dvc-only
depending on use of-R
and the directory queried.Reproduce
In the vscode demo project (which is a subdir) there is a dvc tracked folder (
data/MNIST/raw
) which contains 8 datasets:After deleting
t10k-images-idx3-ubyte.gz
and running the following command:echo 'dot -R from the root lists all' && dvc list . -R --dvc-only && echo '-------------\n-R from the parent directory lists all' && dvc list . data/MNIST -R --dvc-only && echo '-------------\n-R in the directory lists local only' && dvc list . data/MNIST/raw -R --dvc-only && echo '-------------\ndot by itself in the directory shows local only' && dvc list . data/MNIST/raw
the following output is received:
Expected
Consistent behaviour for at least the use of the
-R
flag (i.e -R in the directory listslocal onlyall).Environment information
Output of
dvc doctor
:Additional Information (if any):
Discovered while working through #5712, iterative/vscode-dvc#176 & iterative/vscode-dvc#169. Please reach out on slack if you need any further information.
CC @dberenbaum
The text was updated successfully, but these errors were encountered: