Repository navigation
v0.13.0
A cache that a tool wrote again
Some tools delete the symbolic link and write their cache folder again. The
ledger keeps the record, so exodrive check said Migrated. The card offered a
move back that always failed.
A scan now reads the old path of a moved cache. These cases count as
Rewritten:
- A real folder sits at the path again.
- The link points at another folder.
- Exodrive cannot read the path.
The folder is on this Mac, so its bytes count as local. The card offers
Keep the local folder without a failed press first.
exodrive check
exodrive rollback --keep-local <item>A path that is gone keeps the state it had. So does a record that moved the
data with a tool setting. A record that names another path does not describe
the item, so the scan claims nothing about its link.
Evidence
A fixture home held two Dart caches. The released v0.13.0 binary moved both by
link. A simulated tool then wrote one folder again.
| Step | Result |
|---|---|
check after the tool wrote again |
Dart hosted reads Rewritten with the next step; Dart git reads Migrated |
| Totals | The hosted bytes count as local; the git copy stays on the drive |
rollback dart.pub-cache |
Exit code 1: exists and differs from … |
rollback --keep-local dart.pub-cache |
Exit code 0, copy deleted, record removed |
check after the keep-local |
Dart hosted reads Internal |
A window test drives the same state. The card reads Rewritten, offers
Keep the local folder, and offers no move back or check.