[BUG] Progress polling does not detect terminal events on subsequent pages

Aperta
#1,273 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 4 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
72/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
python, react, typescript
Ambito
api, frontend

Direzione di ricerca

Read the progress endpoint in mod_api/routes/runs.py, the request helper in web/src/lib/api.ts, and the useRunProgress hook. Trace how pagination.next_offset and terminal events are handled, then run or extend the 51 event reproduction described in the issue. Done when polling detects completed or canceled on later pages without duplicates or unnecessary requests.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Description

The frontend progress polling hook appears to consume only the first page of progress events returned by the backend API.

The backend paginates progress events, returning 50 events per page by default. However, the frontend does not appear to follow pagination.next_offset when retrieving progress events.

As a result, if a terminal event such as completed or canceled appears on a subsequent page, the frontend may never detect it and can continue polling indefinitely.

Steps to Reproduce
  1. Configure a run with more than 50 progress events.
  2. Ensure the terminal completed event appears after the first 50 events.
  3. Open the run details page.
  4. Observe the frontend progress polling behavior.
Expected Behavior

The frontend should consume all relevant progress pages and detect terminal events regardless of which page contains them.

Polling should stop when a terminal event (completed or canceled) is detected.

Actual Behavior

The frontend consumes only the first page of progress events.

If the terminal event appears on a subsequent page, it is not detected, and polling continues.

Investigation Details

The issue appears to involve:

  • Backend: mod_api/routes/runs.py — progress endpoint and pagination.
  • Frontend: web/src/lib/api.ts — progress API request.
  • Frontend: useRunProgress hook — polling and terminal-state detection.

An isolated reproduction using 51 events showed:

  • Terminal event within the first 50 events: detected correctly.
  • Terminal event at position 51: not detected; polling continues.

This reproduction used an isolated fixture and does not establish that a production run has encountered the issue.

Suggested Direction

Consider following pagination.next_offset when fetching progress events, ensuring that terminal events on subsequent pages are detected without introducing duplicate events or unnecessary API requests.

I would appreciate maintainer confirmation that this behavior is unintended before proceeding with an implementation.

Environment
  • Repository: CCExtractor Sample Platform
  • API: /api/v1/runs/{run_id}/progress
  • Frontend: React / TypeScript
Lingua principale
Python
Stelle
31
Fork
92
Merge medio
4g 9h
PR unite (30g)
29

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di CCExtractor/sample-platform

Tutte le issue di CCExtractor/sample-platform

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.