[BUG] Progress polling does not detect terminal events on subsequent pages
維護者通常 4 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 3/5
- 預估耗時
- 1-2 天
- 新手友好度
- 72/100
- Issue 類型
- 缺陷
- 描述清晰度
- 描述清楚
- 活躍度
- 活躍
- 技術堆疊
- python, react, typescript
研究方向
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
- Configure a run with more than 50 progress events.
- Ensure the terminal
completedevent appears after the first 50 events. - Open the run details page.
- 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:
useRunProgresshook — 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 小時
- 30 天內合併 PR
- 29
環境準備
- 提供 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
CCExtractor/sample-platform 的其他 Issue
-
[BUG] Unhandled AttributeError on empty database queries for GeneralData and CCExtractorVersion可能已有人在做 @Aspirant200715 於 9 天前認領。 未關閉
難度 3/5 1-2 天 新手友好度 35/100
CCExtractor/sample-platform#1275 · 1 則留言 ·
維護者通常 4 天內回覆
-
[BUG] `TypeError: 'ContentFile' object is not subscriptable` in mod_upload when creating GitHub issue可能已有人在做 @garv-sanveria 於 17 天前認領。 未關閉
難度 2/5 1-3 小時 新手友好度 30/100
CCExtractor/sample-platform#1261 ·
維護者通常 4 天內回覆
-
[BUG] Missing timeouts on 5 outbound HTTP calls outside mod_ci (follow-up to #943)可能已有人在做 @devnishantt 於 54 天前認領。 未關閉
難度 3/5 1-2 天 新手友好度 84/100
CCExtractor/sample-platform#1192 · 2 則留言 ·
維護者通常 4 天內回覆
-
[Feature Request] Improve comparison algorithm to handle frame offsets intelligently (GSoC Qualification)可能重新可做 關聯的 PR 已關閉且未合併。 未關閉
難度 4/5 3-5 天 新手友好度 48/100
CCExtractor/sample-platform#1079 ·
維護者通常 4 天內回覆
-
[BUG] never-worked baseline handling is not fully integrated into trusted CI reporting可能重新可做 關聯的 PR 已關閉且未合併。 未關閉
難度 4/5 3-5 天 新手友好度 42/100
CCExtractor/sample-platform#1057 · 2 則留言 ·
維護者通常 4 天內回覆
查看 CCExtractor/sample-platform 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 62/100
維護者通常 1 天內回覆
-
enhancement
難度 2/5 1-3 小時 新手友好度 68/100
dgunning/edgartools#2019 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 62/100
topoteretes/cognee#6818 · 1 則留言 ·
維護者通常 1 天內回覆
-
source_verification_agent: no outcome when the publisher confirms a work but its DOI resolves to a different record可能已有人在做 @pinjun99 今天認領。 未關閉
難度 2/5 1-3 小時 新手友好度 68/100
Imbad0202/academic-research-skills#1159 · 1 則留言 ·
維護者通常 1 天內回覆
-
[Bug]: DoubleMLData.from_arrays checks the treatment d with force_all_x_finite instead of force_all_d_finite可能已有人在做 @leninworld 今天認領。 未關閉
難度 1/5 1 小時以內 新手友好度 88/100
DoubleML/doubleml-for-py#471 ·
維護者通常 1 天內回覆