Upload 6 files

CHANGELOG.md

@@ -1,10 +1,25 @@
+## v124 — Timeline and Run Explorer stabilization
 
+- Fixed the compact Overall Progress timeline so dynamically visible repair/failure groups cannot wrap dots onto a second row.
+- Removed smooth timeline auto-scroll that could cause visible flicker during polling.
+- Simplified Run Explorer type/status badges to neutral type labels and short status labels such as Success, Failed, Running and Manual.
+- Added regression checks for timeline single-row behavior and compact Run Explorer labels.
 
-## v121 latency/display cleanup
 
-- Reduced perceived latency when re-opening already inspected runs by reusing cached progress/detail payloads immediately and avoiding duplicate polling starts.
-- Added DOM render signatures for run documents, Agent recovery and Gradio endpoint panels to prevent flicker during polling.
-- Preserved heavy hydration in the background for full reports/artifacts while keeping the central panels responsive.
+## v123 — Critical Job launch + failure timeline fix
+
+- Fixed a production-critical HF Job startup failure where the large embedded worker script could make Python fail before startup with `argument list too long`.
+- The worker script is now persisted as `runs/<run_id>/_worker.py` in the mounted run bucket before launch, and the Job receives only `WORKER_SCRIPT_PATH`.
+- Kept a small `WORKER_SCRIPT_B64` fallback only for compatibility/manual launch paths; normal app launches no longer put the worker source in env/argv.
+- Added a failure-log fallback so pre-worker Job failures such as `argument list too long` still create an explicit failed timeline event and red failure point.
+
+## v122 — Stable UI rollback after latency cleanup regression
+
+- Reverted the risky v121 client-side run-detail cache/polling optimizations after they caused build/run UI instability and flicker in real usage.
+- Restored the proven v120 Active Run / Space Test selection and polling behavior while keeping the v118/v119/v120 Pi recovery core intact.
+- Kept the Agent recovery panel, unified agent traces, compact Run Explorer, and blockage protocol UI from the stable v120 line.
+- Removed the v121 rendering-signature shortcuts and progress-payload cache writes that could leave panels in stale or inconsistent states.
+- This release prioritizes correctness and stable polling over speculative latency optimization.
 
 
 ## v120 — Agent recovery UI for blockage protocol

README.md

@@ -42,6 +42,10 @@ The product root `/` is a custom Docker/FastAPI dashboard. `/custom` is kept as
 
 The UI is organized into three main areas:
 
+## v122 stability note
+
+The v122 line intentionally rolls back the experimental v121 client-side caching/polling optimizations after real UI testing exposed flicker and broken build/run behavior. The app keeps the v120 Agent recovery UI and the v118/v119 core blockage protocol, but returns to the proven polling and run-selection model for production stability.
+
 ### Left column
 
 - **Run storage** — check or create the signed-in user's private Bucket.
@@ -205,9 +209,16 @@ A code repair is allowed only when Pi selects `patch_code` and the Factory accep
 
 Repair mode is intentionally strict: it must preserve the original model and real-inference contract, avoid fake/static outputs, keep a cheap health endpoint, and report blockers instead of hiding runtime errors.
 
-## v121 latency/display cleanup
+## v123 — Critical Job launch + failure timeline fix
+
+- Fixed a production-critical HF Job startup failure where the large embedded worker script could make Python fail before startup with `argument list too long`.
+- The worker script is now persisted as `runs/<run_id>/_worker.py` in the mounted run bucket before launch, and the Job receives only `WORKER_SCRIPT_PATH`.
+- Kept a small `WORKER_SCRIPT_B64` fallback only for compatibility/manual launch paths; normal app launches no longer put the worker source in env/argv.
+- Added a failure-log fallback so pre-worker Job failures such as `argument list too long` still create an explicit failed timeline event and red failure point.
 
-- Reduced perceived latency when re-opening already inspected runs by reusing cached progress/detail payloads immediately and avoiding duplicate polling starts.
-- Added DOM render signatures for run documents, Agent recovery and Gradio endpoint panels to prevent flicker during polling.
-- Preserved heavy hydration in the background for full reports/artifacts while keeping the central panels responsive.
+## v124 — Timeline and Run Explorer stabilization
 
+- Fixed the compact Overall Progress timeline so dynamically visible repair/failure groups cannot wrap dots onto a second row.
+- Removed smooth timeline auto-scroll that could cause visible flicker during polling.
+- Simplified Run Explorer type/status badges to neutral type labels and short status labels such as Success, Failed, Running and Manual.
+- Added regression checks for timeline single-row behavior and compact Run Explorer labels.

app.py

@@ -154,12 +154,17 @@ def _events_from_job_logs(log_text: str) -> list[dict[str, Any]]:
     HF Job logs may prefix stdout lines with timestamps, may include ANSI
     sequences, and may sometimes have text after a JSON object. Use
     JSONDecoder.raw_decode from each opening brace instead of json.loads(line)
-    so event extraction is not fragile.
+    so event extraction is not fragile. If the Job fails before the worker can
+    write bucket events, synthesize one explicit failure event so the timeline
+    still shows a red breakpoint instead of appearing empty/broken.
     """
     events: list[dict[str, Any]] = []
     decoder = json.JSONDecoder()
+    clean_lines: list[str] = []
     for raw in (log_text or "").splitlines():
         line = ANSI_RE.sub("", raw).strip()
+        if line:
+            clean_lines.append(line)
         for match in re.finditer(r"\{", line):
             try:
                 payload, _ = decoder.raw_decode(line[match.start():])
@@ -168,6 +173,22 @@ def _events_from_job_logs(log_text: str) -> list[dict[str, Any]]:
             if isinstance(payload, dict) and payload.get("step") and payload.get("status"):
                 events.append(payload)
                 break
+    text = "\n".join(clean_lines).lower()
+    if not events and text:
+        if "argument list too long" in text:
+            events.append({
+                "step": "failure",
+                "status": "failed",
+                "message": "HF Job failed before the worker started: Python argv/env was too large.",
+                "details": {"source": "job_logs", "error": "argument list too long"},
+            })
+        elif any(marker in text for marker in ["traceback", "error", "failed", "exception"]):
+            events.append({
+                "step": "failure",
+                "status": "failed",
+                "message": clean_lines[-1][:500] if clean_lines else "HF Job failed before worker events were written.",
+                "details": {"source": "job_logs"},
+            })
     return events