Skip to content

Conversation

@skshetry
Copy link
Collaborator

@skshetry skshetry commented Jul 9, 2020

The falsy values were being skipped when merging params values
from dvc.yaml and dvc.lock, showing the values as always changed.

These values were never added to info, but were found in
self.params making them appear as changed.

Fixes #4184

  • ❗ I have followed the Contributing to DVC checklist.

  • 📖 If this PR requires documentation updates, I have created a separate PR (or issue, at least) in dvc.org and linked it here.

  • ❌ I will check DeepSource, CodeClimate, and other sanity checks below. (We consider them recommendatory and don't expect everything to be addressed. Please fix things that actually improve code or fix bugs.)

Thank you for the contribution - we'll try to review it as soon as possible. 🙏

The falsy values were being skipped when merging params values
from dvc.yaml and dvc.lock, showing the values as always changed.

These values were never added to `info`, but were found in
`self.params` making them appear as changed.

Fixes iterative#4184
@skshetry skshetry added the bug Did we break something? label Jul 9, 2020
@skshetry skshetry requested review from efiop, pared and pmrowla July 9, 2020 12:00
@skshetry skshetry self-assigned this Jul 9, 2020
@efiop efiop merged commit fe1d7e9 into iterative:master Jul 9, 2020
@skshetry skshetry deleted the fix-4184 branch July 10, 2020 03:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Did we break something?

Projects

None yet

Development

Successfully merging this pull request may close these issues.

dvc status always mark a param as changed

4 participants