Show honest stage and activity feedback during analysis, preview and import #4
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?
Large multi-part exports can spend tens of minutes in analysis or preview with little more than a spinner. Users cannot tell whether work is advancing.
Acceptance criteria:
Starting implementation together with #7 and #8. I have read #14 and all current descriptions/comments. Scope: persisted, owner-scoped server stages and timestamps; distinguish heartbeat from measured activity; inspect the pinned importer reporting contract before exposing counters; remove unsupported analysis percentages; restore status through polling/reconnects. I will work from the latest existing implementation, add focused backend and browser checks, and report exact validation and publication/deployment states. No server rebuild or restart is planned.
Finding: the pinned bridge.4 importer invokes BridgeReport from the final GenerateReport path, not as a live examined/processed event feed. Implementation uses confirmed verification/analysis/import stages and separately labeled worker heartbeat, elapsed time and measured destination activity; it removes the invented analysis 90 percent. Missing/stale status is explicitly unknown. App and processor stage protocol must ship together.
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 #4 CHANGES
The shared panel uses owner-scoped persisted server stages, start/finish times, last confirmed activity and a separately labeled heartbeat. Processor stage records identify verification and metadata analysis while work is actually occurring; the old guessed 90-percent analysis update is gone. A heartbeat never becomes item progress; stale/missing status explicitly means unknown, and polling restores saved state across owner sessions/reconnects. Final elapsed duration freezes at completion; missing timestamps remain unconfirmed.
The pinned bridge.4 BridgeReport hook runs at final report generation, not as a live asset feed. No live examined/processed counters, percentage or ETA are invented. Measured destination requests/new-upload acknowledgements remain separate from final reported assets and processed/skipped items. Final asset totals are labeled as report totals rather than archive entries or a live examined count. See docs/results.md and docs/testing.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. Check authoritative stage/activity feedback against the owner pilot export after a coordinated idle deployment. 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.The shared panel shows persisted server stages, elapsed time, last confirmed activity and a separate worker heartbeat. Missing/stale status remains unknown. No live examined-item count, percentage or ETA is invented from final importer reports, ZIP sizes or elapsed time.
Validation: Backend activity/lifecycle regressions and races, actual processor stage checks and the two-owner-browser activity/reconnect suite 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.