Explain background execution beside the task activity indicator #7
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Users should not have to close a tab experimentally to discover that server-side work continues.
Use one consistent activity panel for analysis, preview and import, following the pilot UX concept: completed/current stages, followed immediately by background-execution reassurance.
Suggested preview copy: “Running on your server. You can close this page. Your preview will continue, and its status and results will be here when you return.”
Acceptance criteria:
Starting implementation together with #4 and #8 after reading #14 and all current comments. Scope: a shared activity panel for analysis, preview and import, with stage/activity information immediately followed by background-execution guidance. Browser-upload guidance will explain that closing the page stops new bytes while accepted bytes remain resumable. Reconnects will use persisted server state; no uninterrupted-restart or automatic-import-retry promise.
Implementation now uses a shared activity panel with server-work guidance directly below the stage list, plus separate browser-upload close/resume guidance. Persisted job/import status is polled on return and in simultaneous sessions. UI production build has passed; focused reconnect/multiple-session browser checks are being added.
Implemented and published for review in commit
e980c3778a76c66c280234e29a3c324f5e7ae56c, branchcodex/issues-4-7-8-activity, PR #17: #17 . The working tree is clean. This supersedes the earlier tooling/validation limitations.VALIDATION
STATE / LIMITS / HANDOFF
Source is committed and pushed for review; not merged, release-image-published or deployed. Forgejo run https://git.sharedroot.net/jchapman/Immich-Bridge/actions/runs/5 is waiting for the AMD64/ARM64 source jobs, with dependent gates blocked. No native release CI pass or native ARM64 execution is claimed. Real large-library performance and deployed pilot behavior remain unverified.
Review #17. It is stacked on #16, which itself follows #15; after those merge, retarget #17 to main and verify the diff and required gates. Coordinate an idle installation of app, runner and processor together, then run an owner pilot preview and check the task lifecycle before closing this issue. Do not interrupt active uploads/tasks for deployment. No automatic import replay, rollback or unsupported mid-import resume is promised.
ISSUE #7 CHANGES
Analysis, preview and import share the same stage/activity panel. Background-execution reassurance is immediately below the stage list, including that closing the page does not request cancellation. It explains that server restarts can interrupt tasks and imports never restart automatically. Stopping has separate wording so it does not promise that a cancelled task will keep running.
Browser-upload guidance explicitly says closing the page stops new bytes, accepted bytes remain resumable, and returning requires selecting the same original ZIPs. Activity reconciles with saved state across reconnects and another owner browser/device. The stage sequences are defined per mode; no invented wizard step number is displayed. See docs/results.md.
Integration handoff: PR #17 is merged into main in
8230741. The final combined source passed local backend/vet/race, UI/browser, container/isolation/HTTPS, source/image policy and secret checks. Detailed merge/conflict evidence and limitations: #14 (comment). Native Forgejo AMD64/ARM64 release validation remains queued; no release images or deployment are claimed. This issue remains open for its pilot checkpoint. Verify background-execution guidance and restored status in the deployed owner workflow. No active upload/task or pilot service was interrupted.Final development handoff: PR #17 is merged into main in
8230741, preserving feature commit(s)e980c37.Background-execution guidance is beside the activity stages. Closing a page does not cancel server work. Browser uploads require continued sending; accepted bytes remain resumable. Server restarts may interrupt tasks and imports do not replay automatically.
Validation: Two-owner-browser checks passed background/upload guidance, reconnect restoration, navigation without cancellation and mobile layout. The disposable upload-reselection/recovery walkthrough passed. The combined application also passed backend/vet/race, UI lint/build, container/HTTPS, source/image policies and secret checks; integration evidence.
Documentation is updated on main through PR #21, merge
5ed7191: feature guide, merged scope/evidence, and remaining pilot checks. All nine documentation/policy tests and link/anchor/workflow checks passed.Closing at the owner's explicit request after merge, local validation and documentation review. This supersedes the earlier request to keep this development issue open through deployment. Native Forgejo AMD64/ARM64 release gates, coordinated idle installation and applicable real-provider/owner pilot checks remain in the release checklist and coordination issue #14. No deployment, native ARM64 pass, real-library capacity result or gate waiver is claimed. PR #19 and scanning remain on hold.