fix(telemetry): classify remaining expected failures in Sentry

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

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

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

研究方向

Start with docs/telemetry.md and tests/telemetry.test.ts to see how expectedOutcome is defined and asserted, then audit each named Sentry group against the code that emits it, e.g. src/server/baguette-runtime.ts:77, src/ui/simulator-panel.ts:868, and the serve-emu/UI discovery paths. Check the 5 s simctl launchctl list deadline before filtering device-apps timeouts. Done means every listed failure has a classification, metric, or sample decision and the telemetry docs and tests match.

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

描述

enhancement

Commit 44f1b66 added expectedOutcome, but these user-environment and host-lifecycle failures are still not classified, so they keep being reported as errors. Each one should map to an expected outcome, be counted as a metric, or be sampled.

Toolchain missing (unsupported_platform or a new toolchain_missing)

  • Baguette Swift runtime libraries (src/server/baguette-runtime.ts:77): 3T, 2V
  • spawn /usr/bin/xcrun ENOENT: 9S, likely also 8Q (ios.devices.discovery, 69 users)
  • devicectl "requires Xcode 27": 4E, 21

Device-apps discovery deadlines

  • termination === "deadline" is deliberately left unclassified: 2N (ios_simulator_apps, 108 users), 3W, 61, 4V, 3C
  • Before filtering, check whether the 5 s simctl launchctl list limit is too tight. Consider raising it to about 15 s.
  • The same applies to UI discovery timeouts: UI-P

Physical iOS connection state (device_unavailable)

  • ios_physical_* causes connection_failed, connection_timeout, service_open_failed, service_open_timeout, query_timeout: 4B, 2W, 43
  • "iPhone no longer connected": 7P
  • "Connect the paired iPhone": 22
  • "adapter closed": 7V

Other server errors

  • Processes killed by signal (process_signalled → cancelled): AD, AC
  • adb timeouts and offline devices in serve-emu (device_unavailable): 7
  • ServeEmu.device: 1Q
  • Screenshot HTTP 400 (device_unavailable): 2T
  • Display FPS requires Android 12 (unsupported_platform): 9Y; FPS monitor already exists (invalid_input): 9F
  • "no accessibility data": 39, R. Also route plugin.ts:321 through describeUi so it gets the existing restart recovery.
  • tvOS or no-bezel simulators, definition.json 404 (unsupported_platform, fall back to no bezel): 29, 8X
  • Generic TimeoutError on tool deadlines (count as a metric, keep sampled): 2X, 36, X
  • app_flow "No package.json found" (invalid_input): A2

UI / host lifecycle

  • host_unavailable / session_closed outcomes:
    • UI-15, "app-server process is not available"
    • UI-12, "Transport closed"
    • UI-2X, "MCP client is shut down"
    • UI-2T, "composer unavailable"
    • UI-1F, "MCP app identity changed"
  • Best-effort cleanup calls that time out (*_close, *_reset, mobile_check_plugin_update, mobile_logs_close) should be counted as metrics, not captured as exceptions:
  • Small fixes while you're in there:
    • Guard setPointerCapture (src/ui/simulator-panel.ts:868, UI-2W)
    • Handle EPIPE on writes to a closed helper in resources.read (SERVER-A4)

Update docs/telemetry.md and tests/telemetry.test.ts to match.

主要語言
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 摘要。