Repository navigation
v0.18.0
Two folders called bun cache
bun 1.4 fills <BUN_INSTALL>/install/cache: an install writes the packages
there. The provider also read ~/Library/Caches/bun. That folder came from an
earlier guess, and bun never reads it.
The provider now reads the folder that bun prints, then the install folder that
BUN_INSTALL names. The guess is gone, so a scan cannot describe a link that no
tool follows.
This Mac showed both halves of the problem:
Bun Package Cache package_store 235.4 KB Blocked symlink /Users/…/.bun/install/cache
└── [!] Exodrive recorded a move of /Users/…/Library/Caches/bun. This tool reads
/Users/…/.bun/install/cache. Run 'exodrive rollback bun.cache' to return the copy.
A test run moved a folder from this Mac, and the record named it after a folder
that bun stopped reading. The card claimed Migrated, so nothing showed the
mismatch.
A record speaks only for the folder that it moved
The scan now compares the recorded folder with the folder that the item
reports. When they differ, the row keeps its place but takes no move claim, and
the reason names the recorded folder, the folder that the tool reads, and the
rollback command.
exodrive migrate also refuses an item whose ID has a record, so the row cannot
hide behind a second move.
The repair on this Mac:
$ exodrive rollback bun.cache
Restored bun.cache. The ledger record is removed.
$ exodrive check
bun.cache | /Users/…/.bun/install/cache | 241090 | migrated=false | blocked=-
The copy is back at ~/Library/Caches/bun, which holds 1.8 MB. bun does not
read that folder, so you can delete it. Exodrive does not delete data on its
own.
What this release does not prove
The @t@ files in ~/Library/Caches/bun came from a bun build that this
version does not reproduce on this Mac. bun 1.4.2 wrote every probe install into
install/cache and none into ~/Library/Caches/bun, so Exodrive follows the
folder that bun fills.