Show truthful task activity and confirm server-task cancellation

jchapman commented

2026-10-25 20:30:46 +00:00

Owner

Large exports previously offered a spinner or estimated analysis percentage, and analysis had no Stop control. Analysis, preview and import now share persisted stage/activity timestamps and a reconnecting activity panel. Worker heartbeat is labeled separately from actual activity; final importer asset counts are not presented as live examined-item counters. Background-execution guidance sits beside the stage list and distinguishes browser uploads.

Stop requests are owner-scoped and idempotent. Queued analysis is fenced before a worker claim; running tasks show Stopping until process/container and staging cleanup are confirmed. Completion can win a late stop. Accepted ZIPs, reusable completed analysis and existing Immich assets remain; interrupted imports never replay automatically. Cleanup uncertainty reports Interrupted with an administrator recovery action.

Validation: local Linux AMD64 Docker backend tests/vet, focused API and runner race tests, pinned importer fixtures, real processor isolation/stage messages and importer cancellation/final log flush; UI lint/build, two-browser activity/reconnect/cancellation checks and the disposable full browser walkthrough; HTTPS/upload-resume/readiness checks; nine CI contract/policy tests; source secret scan; gosec and govulncheck against the unchanged reviewed policy (29 findings across 35 production files, no loading errors or suppressions). The final committed-image full smoke check passed; detailed results are recorded in the linked issue handoffs.

Refs #4, #7 and #8; workflow and scope follow #14. These issues remain open for review and the deployed pilot checkpoint. No service was restarted for deployment and no real photo library was used. Native ARM64 and dedicated release CI remain unverified; no release gate is waived. The UI retains its existing large-bundle advisory.

Stacked on #16 (codex/issue-2-oidc-availability) to preserve the current validated baseline, which itself depends on #15. After those merge, retarget this PR to main and verify the resulting diff and required CI. Install app, runner and processor together only after coordinating an idle window.

Forgejo CI: run 5 is waiting for AMD64/ARM64 source jobs; dependent gates are blocked. Local verification does not replace those release gates.

Large exports previously offered a spinner or estimated analysis percentage, and analysis had no Stop control. Analysis, preview and import now share persisted stage/activity timestamps and a reconnecting activity panel. Worker heartbeat is labeled separately from actual activity; final importer asset counts are not presented as live examined-item counters. Background-execution guidance sits beside the stage list and distinguishes browser uploads. Stop requests are owner-scoped and idempotent. Queued analysis is fenced before a worker claim; running tasks show Stopping until process/container and staging cleanup are confirmed. Completion can win a late stop. Accepted ZIPs, reusable completed analysis and existing Immich assets remain; interrupted imports never replay automatically. Cleanup uncertainty reports Interrupted with an administrator recovery action. Validation: local Linux AMD64 Docker backend tests/vet, focused API and runner race tests, pinned importer fixtures, real processor isolation/stage messages and importer cancellation/final log flush; UI lint/build, two-browser activity/reconnect/cancellation checks and the disposable full browser walkthrough; HTTPS/upload-resume/readiness checks; nine CI contract/policy tests; source secret scan; gosec and govulncheck against the unchanged reviewed policy (29 findings across 35 production files, no loading errors or suppressions). The final committed-image full smoke check passed; detailed results are recorded in the linked issue handoffs. Refs #4, #7 and #8; workflow and scope follow #14. These issues remain open for review and the deployed pilot checkpoint. No service was restarted for deployment and no real photo library was used. Native ARM64 and dedicated release CI remain unverified; no release gate is waived. The UI retains its existing large-bundle advisory. Stacked on #16 (`codex/issue-2-oidc-availability`) to preserve the current validated baseline, which itself depends on #15. After those merge, retarget this PR to main and verify the resulting diff and required CI. Install app, runner and processor together only after coordinating an idle window. Forgejo CI: [run 5](https://git.sharedroot.net/jchapman/Immich-Bridge/actions/runs/5) is waiting for AMD64/ARM64 source jobs; dependent gates are blocked. Local verification does not replace those release gates.

jchapman added 1 commit

2026-10-25 20:30:46 +00:00