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
Interesting detail: if params.yaml is committed to git - everything works: git clone https://github.com/Danila89/dvc_empty.git && cd dvc_empty && git pull --all && git checkout dvc_data_status_issue && dvc data status
The text was updated successfully, but these errors were encountered:
Interesting detail: if params.yaml is committed to git - everything works:
That makes sense because dvc data status is comparing changes in the workspace to the Git HEAD (like a companion to git status). Once again, DVC considers the Git HEAD invalid here because there's no params.yaml. So I would say the behavior is expected, but we need a better error message.
Description
dvc data status
fails when hydra integration is involved.Reproduce
git clone https://github.com/Danila89/dvc_empty.git && cd dvc_empty && dvc exp run -n something && dvc data status
Expected
dvc data status
outputEnvironment information
Output of
dvc doctor
:Additional Information (if any):
Interesting detail: if
params.yaml
is committed to git - everything works:git clone https://github.com/Danila89/dvc_empty.git && cd dvc_empty && git pull --all && git checkout dvc_data_status_issue && dvc data status
The text was updated successfully, but these errors were encountered: