-
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
cache file name automatically changed #3680
Comments
Hi @lmxs1237, I notice that you are using a very old version (recent release is |
Hi @skshetry, I updated the version of dvc to v0.93.0, but it happened again. And I tried to change the cache file name with |
Can you check via
Can you also check that specific cache content if it's a json? To me, it looks like someone changed |
@skshetry Funny thing.. When I finished typing above words, 3 more cache file's name changed.. |
Whoa, that is extremely strange 👀 Having those |
@lmxs1237 It would help us a lot if you could come up with a minimal reproducible script. |
@lmxs1237 Are you sure you are not doing something weird with your cache? Or maybe this project is also used by someone else and they might be doing something odd to it? This looks really odd and I have hard time thinking that it has been a bug since at least 0.66.0 (but maybe it is so obscure and specific that it only happens in specific circumstances, we'll see). As a sanity check, could you run |
The cache is exactly the same file with the original one. Sound like there is a program automatically adding a suffix to the cache file according to its file format whenever it reads. |
Closing as stale. |
dvc version 0.93.0
What I did is using
dvc run
to run python code, anddvc add
for dependencies.Then changed one of the dependencies,
dvc run
again, anddvc add
for the changed fileThe cache for files automatically changed.
For example, for csv file
cache
- e2
- 83742f43b84506f6417e43f6ba666b
became
cache
- e2
- 83742f43b84506f6417e43f6ba666b.csv
which makes me unable to do dvc checkout.
Does anyone have idea about this? Thanks
The text was updated successfully, but these errors were encountered: