Home

dev / openkara

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

fix(remote): revert unimplemented capability flags, reset transfer progress on failure

2 months ago

c5a53c5
Authored
Davy7/20/2026, 8:20:31 PM
- DropboxProvider, GoogleDriveProvider, and WebDAVProvider now report
  resumable_upload and range_download as false. The helper functions
  (dropbox_resumable_upload, google_drive_resumable_upload) exist but
  are not yet wired to the resumable_upload_bytes and download_range
  trait methods. Advertising support without an implementation caused
  callers to route to the default trait method, which returns a
  non-retryable ProviderCapabilityUnavailable error — making large
  database publishes to Dropbox/Google Drive fail permanently and
  resumable downloads fail on the first chunk.
- resumable_atomic_download now resets the transfer-part row's
  transferred_bytes to 0 and state to 'failed' when a range download
  fails and the temp file is removed. Without this, the next run sees
  a matching part row with a non-zero offset but no temp file, resets
  offset to 0 internally, then overwrites the DB row after the first
  chunk — creating an inconsistent state where the DB claims progress
  the file does not have.

Parent32bb84d

4 files changed
  • src-tauri/src/remote/atomic_download.rs+24−2
  • src-tauri/src/remote/dropbox.rs+10−3
  • src-tauri/src/remote/google_drive.rs+10−5
  • src-tauri/src/remote/webdav.rs+7−1