Home

dev / openkara

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

fix(remote): unique batch operation ids, filter phantom uploads, migrate fallback DB

2 months ago

1f0304e
Authored
Davy7/20/2026, 8:11:13 PM
- record_prepared_operation now uses a unique timestamp-based id
  (publish-batch-<ms>) for batch mutations instead of the constant
  publish-batch, preventing primary-key collisions across sequential
  or concurrent mutations.
- get_all_upload_statuses filters out Publish rows whose payload has
  empty song_ids. These batch placeholder rows are internal outbox
  bookkeeping for recovery; surfacing them produced a phantom Running
  upload entry that never completed and persisted across restarts.
- The in-memory control DB fallback (when the file-backed DB fails to
  open) now applies remote-state migrations so recovery and upload-status
  queries do not hit no-such-table errors in degraded mode.

Parent509762a

3 files changed
  • src-tauri/src/remote/mutation.rs+12−7
  • src-tauri/src/remote/sync/upload_status.rs+58−0
  • src-tauri/src/state/remote.rs+8−3