Home

dev / openkara

publicthedavidweng/OpenKara· sync paused
Overview Code History Branches Pull requestsIssuesInsights
main
HomeOverview Code PRsIssues

fix(remote): content-addressed assets and immutable candidate recovery (#151)

2 months ago

340552f
Authored
Davy7/22/2026, 2:41:40 AM
Apply the PR #175 comprehensive reliability patch on e4ea3be:

- Resume exact-byte immutable candidates; never rebuild from a newer working DB
- Persist and recheck referenced-asset fingerprints before manifest CAS
- Publish media/stems/artwork under content-addressed paths
- Scope generation DB objects by operation hash to avoid concurrent collisions
- Keep GC from deleting other writers' in-flight staging data
- Repair restart digests only from Clean with no active operation

Also allow directory bulk-upload helpers that the CAS path no longer calls so
clippy -D warnings stays clean.

Parente4ea3be

11 files changed
  • src-tauri/src/library/artwork.rs+36−7
  • src-tauri/src/remote/atomic_download.rs+55−12
  • src-tauri/src/remote/control_db.rs+6−1
  • src-tauri/src/remote/dropbox.rs+2−0
  • src-tauri/src/remote/executor.rs+700−270
  • src-tauri/src/remote/google_drive.rs+2−0
  • src-tauri/src/remote/manifest.rs+94−2
  • src-tauri/src/remote/provider.rs+4−0
src-tauri/src/remote/sync/file_ops.rs
+2
−0
  • src-tauri/src/remote/sync/publish.rs+224−111
  • src-tauri/src/remote/webdav.rs+5−0