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

Abierto
#1,273 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 4 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
72/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
python, react, typescript
Área
api, frontend

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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
Lenguaje dominante
Python
Estrellas
31
Forks
92
Merge medio
4 d 9 h
PR fusionados (30 d)
29

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de CCExtractor/sample-platform

Todos los issues de CCExtractor/sample-platform

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.