feat(ui): queue position, elapsed time, filename, CPU-mode notice #46
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/ui-polish"
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?
Summary
Addresses user confusion where a freshly-submitted job sits in
pendingfor minutes with no explanation (single-worker queue + CPU-mode OCR).FileRef.display_name(optional metadata) — UI preserves client-provided upload filename; pipeline ignores it for execution. Backward compatible with older stored rows.jobs_repo.queue_position(job_id)→(ahead, total_active). Fragment renders "Queue position: N ahead — M jobs total in flight (single worker)" / "About to start — the worker just freed up".Running for MM:SS) and finished (Finished in MM:SS)./healthzgains additiveocr_gpu: true | false | nullkey (not part of the gate). Surya recordstorch.cuda.is_available()on first warm-up; UI surfaces a CPU-mode notice when false.<progress>, live dot via CSS animation.<title>includes the job id.Test plan
uv run pytest tests/unit tests/integration -v— 321 green (272 unit, 49 integration).curl http://192.168.68.42:8994/healthzreturns the newocr_gpukey.curl http://192.168.68.42:8994/ui/jobs/ef08e00c-0b40-43ec-9ec9-58af136dc3d3/fragmentrenders without crashing on legacy rows that lackdisplay_name.🤖 Generated with Claude Code