add: support rollback/recovery from partial/failed dvc add
See original GitHub issueIf the user does a long running dvc add directory that dies somewhere in the middle, there is no obvious (to the user) way to recover from the state where
- DVC has not generated a .dvc file
- half of the users files are still in the workspace (and have not been moved into cache)
- half of the user’s files have been moved into cache, but have not been checked out/linked (and now appear to be lost)
Currently it’s possible to recover from this state manually as long as we have the .dir
file for the original complete directory, but not in a straightforward way
discord context https://discord.com/channels/485586884165107732/485596304961962003/872423982463340555
Issue Analytics
- State:
- Created 2 years ago
- Comments:15 (7 by maintainers)
Top Results From Across the Web
checkout | Data Version Control - DVC
This command will fail to checkout files that are missing from the cache. In such a case, dvc checkout prints a warning message....
Read more >how to return back to an older version of data #599 - GitHub
Hi,. If i change a data file (let's say my training set) and then run dvc repro. How do i revert back to...
Read more >Delphix Engine 4.3
Delphix Customer Support will provide and install any patch or upgrade that ... VDB rollback would fail due to "Failed to apply logs...
Read more >Roll back and delete recovery
To find this module, navigate to Rollback & Recovery > Delete Recovery. Script Execution History module. This module works on scripts executed ...
Read more >Broadcom Mainframe Product Maintenance
RC/Query for Db2 for z/OS, 20.0, 2021-12-17, LU03935, TS-UA REPORT FAILS WHEN USING ... Datacom/AD, 15.1, 2021-12-20, LU03986, PRODUCT PTF ANALYSIS SUPPORT ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’m bumping the priority here, we already have a guideline against breaking the user’s workspace, so we need to realize the correct implementation.
Another user nearly lost their ~140GB of data. We should take data loss seriously. Even if we don’t add a support for transactions (rollback/commit), we should not break user’s workspace by moving files to the cache.
Suggestion: at least prioritize to implement a progress bar to show the ETA. Lack of pb was the reason I was interupted the add process. Thanks again for the support for getting the data back.