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

オープン
#1,273 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 4 日以内に返信

まだ誰も着手していません。

評価

難易度
3/5
見積もり時間
1〜2日
初心者へのやさしさ
72/100
issue の種類
バグ
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
python, react, typescript
領域
api, frontend

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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
主要言語
Python
スター
31
フォーク
92
平均マージ
4日 9時間
マージ済み PR(30日)
29

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

CCExtractor/sample-platform のほかの issue

CCExtractor/sample-platform の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。