mirror of
https://github.com/immich-app/immich
synced 2026-08-15 13:03:57 +00:00
429e181c8f
onIosUpload runs sync local, sync remote, hash and handle backup sequentially. on the bg refresh task path that's a 20s budget from iOS, and sync + hash usually eat all of it before backup gets a turn to enqueue any candidates. these phases don't actually depend on each other. local + remote sync touch different tables. hash works off whatever's already in drift. handle backup reads candidates and just enqueues to URLSession bg. anything one phase produces in this fire shows up to the others on the next fire, and server-side dedup catches the rare race where backup enqueues something sync remote was about to mark as already uploaded. so this runs all four concurrently via Future.wait, with hash getting the full maxSeconds-1 budget instead of a fixed 5s. outer budget timeout still caps everything before iOS expires. second small change: getAssetsToHash orders by createdAt DESC instead of id ASC to match getCandidates. when hash runs inside a refresh fire it processes recent photos first. |
||
|---|---|---|
| .. | ||
| drift_schema_v1.json | ||
| drift_schema_v2.json | ||
| drift_schema_v3.json | ||
| drift_schema_v4.json | ||
| drift_schema_v5.json | ||
| drift_schema_v6.json | ||
| drift_schema_v7.json | ||
| drift_schema_v8.json | ||
| drift_schema_v9.json | ||
| drift_schema_v10.json | ||
| drift_schema_v11.json | ||
| drift_schema_v12.json | ||
| drift_schema_v13.json | ||
| drift_schema_v14.json | ||
| drift_schema_v15.json | ||
| drift_schema_v16.json | ||
| drift_schema_v17.json | ||
| drift_schema_v18.json | ||
| drift_schema_v19.json | ||
| drift_schema_v20.json | ||
| drift_schema_v21.json | ||
| drift_schema_v22.json | ||
| drift_schema_v23.json | ||
| drift_schema_v24.json | ||
| drift_schema_v25.json | ||
| drift_schema_v26.json | ||
| drift_schema_v27.json | ||
| drift_schema_v28.json | ||