MC-4613 — SW: bounded-but-generous timeout for / and /ticket/ navigations

Home Board MC-4613

SW: bounded-but-generous timeout for / and /ticket/ navigations

Follow-up from MC-4607 council. MC-4607 made Home '/' network-first with NO abort timeout (mirrors /ticket/ MC-3749) to stop heavy-but-healthy renders serving offline.html. Risk...

State Done Next Action Closed Owner Luci Runtime Closed Age 11d ago

← MC-4613

Ticket is done; runtime is closed. · profile claude_opus_1m_medium

Description

MC-4613

Follow-up from MC-4607 council. MC-4607 made Home '/' network-first with NO abort timeout (mirrors /ticket/ MC-3749) to stop heavy-but-healthy renders serving offline.html. Risk (Opus+GLM): a STALLED socket (TCP open, server hung mid-render) leaves respondWith pending until the OS/browser socket timeout (minutes) with no offline fallback. Better: a generous-but-finite AbortSignal (~15-20s) on both '/' and '/ticket/' — long enough for a slow render, short enough to fall back on a dead socket. Apply to both for consistency.

Activity

done

Luci is working...

Details — Done · Low · Luci ▼

State

Done

Closed

State

Priority

People

Owner (assigned to)

Controller

Timing / Details

Due Date

Snooze

Source api (human)

Project Mission Control

Created 11d ago

Updated 6d ago

Advanced / Operator evidence

Routing owner

Routes via

Operator console

Evidence

Ticket is done; runtime is closed. MC is visibility-only. Hermes Luci launches and gates work outside MC, then mirrors evidence/status here.

Workflow

Start Dev Review + QA ▾

Select phases to include:

Research (scott) Implement (larry) (required) Council Review (council) Code Review (luci) Validate (tessa) (required) Sign-off (atlas)

Agents

Review Gates

Decision

WAT routing: choose an agent, review gate, or decision. Buttons use the live runtime when one is attached.

codexbuilder 6d ago

MC-4613 implementation evidence: committed b31a88c on branch kb/mc-4613-sw-timeout in /home/lucienne/workspace/state/kanban-worktrees/mc-4613-sw-timeout. Changes: - static/sw.js adds NAVIGATION_NETWORK_TIMEOUT_MS=18000 and uses fetchWithTimeout for both '/' and '/ticket/' navigation branches. - Existing cache/offline fallbacks are preserved for both branches. - app.py and sw cache/asset versions bumped. - tests/test_service_worker_timeouts.py adds regression coverage for the generous finite timeout. Verification: - uv run --with pytest python -m pytest tests/test_service_worker_timeouts.py -q -> 5 passed - uv run --with pytest --with flask --with flask-sock --with pyyaml --with croniter python -m pytest tests/test_ticket_runtime_regressions.py::TicketRuntimeAssetRegressionTests::test_chat_asset_version_busts_stale_websocket_auth_clients -q -> 1 passed - node --check static/sw.js -> exit 0 Note: graphify update . was attempted per repo guidance but the local graphify shim is broken: ModuleNotFoundError: No module named 'graphify'. Ready for review; no merge/restart/deploy performed.

luci-board-manager 6d ago

Controller action: routed this Luci-owned technical follow-up through Hermes Kanban mc-internal as t_37d4eef1 (codexbuilder). MC remains visibility-only; no MC runtime/pickup was started. The Kanban worker must append commit/test evidence or a blocker here before this MC ticket is closed.

luci-board-manager 6d ago

Controller recovery: the first Kanban dispatch for t_37d4eef1 spawned in the live mission-control checkout, so I reclaimed it before accepting work and retargeted the same Kanban card to isolated worktree /home/lucienne/workspace/state/kanban-worktrees/mc-4613-sw-timeout. Redispatch will run from that worktree; MC remains visibility-only.

luci-board-manager 6d ago

Controller gate complete (visibility-only): landed and deployed MC-4613 without using MC pickup/runtime. Evidence: worker commit b31a88c independently reviewed PASS; cherry-picked to mission-control master as 77e22ef1a4be66fc228a9564d3528a4ab9353048; pushed origin/master; graphify update . completed; tests passed on live checkout (`tests/test_service_worker_timeouts.py` 5 passed, targeted ticket-runtime asset regression 1 passed, `node --check static/sw.js` exit 0); restarted system luci-dashboard.service; smoke checks returned 200 for /api/health, /api/v1/tickets?limit=1, /, and /board on port 3001. Service-worker navigation fetches for / and /ticket/ now use bounded 18s timeout with cache/offline fallback preserved.

Live ▼

No activity yet

←