fix(ui): stop reconnect and polling loops when the host thread is gone

未關閉
#43 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
45/100
Issue 類型
缺陷
描述清晰度
描述清楚
活躍度
活躍
技術堆疊
typescript
領域
devtools

研究方向

Start with ReconnectLoop.run in src/ui/reconnect.ts (lines 26-37), where retries currently ignore everything except StopReconnectError. Then check how the host_thread_missing error reaches the logs and stream panels (src/ui/logs-panel.ts around 239-243, src/ui/simulator-panel.ts around 518), and the timers in src/ui/plugin-updates.ts:48 and src/ui/simulator-panel.ts:776. Done means that a missing thread stops every timer and shows "Session closed" in the panel, and that the loop no longer calls the host.

由索引模型根據 Issue 內容生成。

描述

bug

Problem

When the Codex thread behind a panel is gone, UI panels keep calling the host forever. Host calls fail with MCP error -32600: thread not found, and the panel retries roughly every 10 s with no end.

Cause

  • ReconnectLoop.run (src/ui/reconnect.ts:26-37) retries every error that is not a StopReconnectError, with backoff capped at 10 s.
  • "thread not found" arrives as a JSON-RPC McpError, not an isError result, so src/ui/logs-panel.ts:239-243 never turns it into a stop.
  • The stream panel starts the same loop at src/ui/simulator-panel.ts:518.
  • These other timers also never check for a dead thread:
    • the plugin-update interval (src/ui/plugin-updates.ts:48)
    • device-apps discovery (src/ui/simulator-panel.ts:776)

Commit 44f1b66 now classifies host_thread_missing as session_closed and stops reporting it, so it disappears from Sentry. The loop still hits the host, and probably adds to the "App server request queue is full" errors.

Evidence (Sentry)

Suggested fix

Treat host_thread_missing as terminal in these places:

  • ReconnectLoop
  • the logs and stream receive paths
  • device-apps discovery
  • the plugin-update interval

Then stop all timers and show "Session closed" in the panel.

主要語言
C++
星號
243
分支
21
平均合併
15 小時 6 分鐘
30 天內合併 PR
57

環境準備

  • 沒有 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

callstackincubator/codex-mobile-dev-plugin 的其他 Issue

查看 callstackincubator/codex-mobile-dev-plugin 的全部 Issue

相似的 Issue

更多 C++ Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。