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
Everything is ok. Note that there is no problem with variables in deps section.
Reproduce
Just create synth pipeline with the template variable in path to some params file.
Expected
I think that DVC should build & compare paths with the same logic for deps and params sections. It looks like DVC doesn't understand that variable in YAML is the same that dvc.lock has.
So the problem is that ${PPL_PTH}/config.yaml/config.yaml in params is not getting expanded to pipelines/02_seg/config.yaml in dvc status, correct? Is it a problem for other commands as far as you know? Where is ${PPL_PATH} defined?
So the problem is that ${PPL_PTH}/config.yaml/config.yaml in params is not getting expanded to pipelines/02_seg/config.yaml in dvc status, correct? Is it a problem for other commands as far as you know? Where is ${PPL_PATH} defined?
I think yes. Command dvc commit -f also not able to catch that no changes are necessary. Parameter ${PPL_PATH} is defined in params.yaml. As I remember definition in vars section doesn't help also.
@skshetry will know better how the internals work here, but I think DVC loads the parameters first to then fill variables from the dvc.yaml template. So I think it becomes circular to use those variables to read the path to the parameters file. Maybe we should note in the docs that variables cannot be in the params section.
Sorry, the above looks to be incorrect on further inspection. Can you share the params.yaml? So far, I can't seem to reproduce the issue.
Bug Report
Description
I have the following dvc pipeline with the following stage:
Its compiled version for one of the datasets is:
You can see here, that variables were correctly replaced by real values. But there is a problem:
and
dvc commit --force
doesn't help:But if I replace
with the
Everything is ok. Note that there is no problem with variables in
deps
section.Reproduce
Just create synth pipeline with the template variable in path to some params file.
Expected
I think that DVC should build & compare paths with the same logic for
deps
andparams
sections. It looks like DVC doesn't understand that variable in YAML is the same that dvc.lock has.Environment information
Ubuntu
Output of
dvc doctor
:Additional Information (if any):
The text was updated successfully, but these errors were encountered: