Skip to content
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

File sync status isn't updated in the UI after dvc push #1813

Closed
alex000kim opened this issue Jun 2, 2022 · 3 comments
Closed

File sync status isn't updated in the UI after dvc push #1813

alex000kim opened this issue Jun 2, 2022 · 3 comments

Comments

@alex000kim
Copy link

See https://www.loom.com/share/52defce18bc74e84aef75b0225880a9c

I've changed the data, and ran dvc push, but the UI doesn't reflect that.
Initially, I thought that maybe it might simply take a while because I have over 1300 files.
But it's been over 10 min now...

@mattseddon
Copy link
Member

Relates to #1769 and #1799 (comment).

Currently, the SCM view does not reflect the remote at all. In the view shown those files are under the "Ready for Git Commit" section. This means that as far as DVC is concerned there is no further action to take in terms of updating the cache but there is a difference between what is in the workspace and the previous commit (i.e dvc status is clean but dvc diff has entries). Committing the dvc.lock to git should empty the view.

For extra information please see #772. We've been through a few iterations on how to display this complexity. I'm open to any suggestions that you have.

Thanks!

@alex000kim
Copy link
Author

Oh ok, that makes sense after the explanation, but the behavior is indeed counterintuitive as described in #1769

Feel free to close this one.

@mattseddon
Copy link
Member

Thanks. Please add anything that could be useful to #1769 👍🏻.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants