Bug: 80% progress is meaningless - hardcoded before health check starts #9

New issue

Closed

opened 2026-05-01 00:47:23 +00:00 by Mark · 1 comment

Mark commented

2026-05-01 00:47:23 +00:00

Owner

Bug: 80% progress is meaningless - hardcoded before health check starts

Location: backend/app/services/process_manager.py lines 229-235

Current behavior:

# Phase 3: Wait for ready
progress.phase = LoadingPhase.WARMING_UP
progress.progress = 80.0
progress.message = "Waiting for server to be ready..."
progress.notify()

await self._wait_for_ready(process_id, backend, port)

The 80% is hardcoded immediately BEFORE _wait_for_ready() starts its polling loop. It has no connection to any actual progress calculation - it's just a phase label set at the start of the waiting period.

Expected:

Progress should either reflect actual health check attempts (e.g., 80% + (elapsed/timeout) * 20%)
Or remove the false progress indicator entirely and just show "warming up" or "checking health..."

Impact:

User sees 80% and thinks "almost done" when actually the process may just be starting its health check loop
Misleading UX - progress stays at 80% for the entire duration (up to 600s timeout)

**Bug:** 80% progress is meaningless - hardcoded before health check starts **Location:** `backend/app/services/process_manager.py` lines 229-235 **Current behavior:** ```python # Phase 3: Wait for ready progress.phase = LoadingPhase.WARMING_UP progress.progress = 80.0 progress.message = "Waiting for server to be ready..." progress.notify() await self._wait_for_ready(process_id, backend, port) ``` The 80% is hardcoded immediately BEFORE `_wait_for_ready()` starts its polling loop. It has no connection to any actual progress calculation - it's just a phase label set at the start of the waiting period. **Expected:** - Progress should either reflect actual health check attempts (e.g., 80% + (elapsed/timeout) * 20%) - - Or remove the false progress indicator entirely and just show "warming up" or "checking health..." - **Impact:** - User sees 80% and thinks "almost done" when actually the process may just be starting its health check loop - - Misleading UX - progress stays at 80% for the entire duration (up to 600s timeout)