fix(telemetry): classify remaining expected failures in Sentry
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 32/100
- Issue 類型
- 缺陷
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- typescript
研究方向
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 內容生成。
描述
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 listlimit 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_*causesconnection_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:321throughdescribeUiso it gets the existing restart recovery. - tvOS or no-bezel simulators, definition.json 404 (
unsupported_platform, fall back to no bezel): 29, 8X - Generic
TimeoutErroron 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_closedoutcomes:- 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:
Update docs/telemetry.md and tests/telemetry.test.ts to match.
- 主要語言
- C++
- 星號
- 243
- 分支
- 21
- 平均合併
- 15 小時 6 分鐘
- 30 天內合併 PR
- 57
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
callstackincubator/codex-mobile-dev-plugin 的其他 Issue
-
enhancement
難度 4/5 3-5 天 新手友好度 35/100
callstackincubator/codex-mobile-dev-plugin#119 ·
維護者通常 1 天內回覆
-
documentation
難度 3/5 1-2 天 新手友好度 45/100
callstackincubator/codex-mobile-dev-plugin#117 ·
維護者通常 1 天內回覆
-
enhancement
難度 3/5 1-2 天 新手友好度 45/100
callstackincubator/codex-mobile-dev-plugin#116 ·
維護者通常 1 天內回覆
-
enhancement
難度 3/5 1-2 天 新手友好度 55/100
callstackincubator/codex-mobile-dev-plugin#115 ·
維護者通常 1 天內回覆
-
bug
難度 3/5 1-2 天 新手友好度 45/100
callstackincubator/codex-mobile-dev-plugin#114 ·
維護者通常 1 天內回覆
查看 callstackincubator/codex-mobile-dev-plugin 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 72/100
CachyOS/packageinstaller#144 ·
維護者通常 1 天內回覆
-
documentation
難度 1/5 1 小時以內 新手友好度 82/100
TomerAberbach/profiler-md#951 ·
維護者通常 1 天內回覆
-
[Bug] Default key routing (JavaStringHash) picks a different partition than the Java client for about half of keys可能已有人在做 @0z5a 今天認領。 未關閉
難度 2/5 1-3 小時 新手友好度 82/100
apache/pulsar-client-go#1575 ·
維護者通常 2 天內回覆
-
難度 2/5 1-3 小時 新手友好度 72/100
pocoproject/poco#5764 ·
維護者通常 2 天內回覆
-
bug cpp-core-guidelines low-priority
難度 2/5 1-3 小時 新手友好度 62/100
NatronGitHub/openfx-supportext#164 ·
維護者通常 1 天內回覆