Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

iOS Simulator open: simctl openurl has no timeout and can hold the open until the daemon request times out

已关闭
#3,101 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
78/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
ios, typescript
领域
mobile, testing

调研方向

Start in packages/platform-apple/src/core/app-launch.ts at openIosSimulatorUrl and compare its simctl bounds with the other launch calls. Add the unit test described for a provider whose openurl never returns, then verify the open fails within the bound with the typed reason and that cancellation kills the child. Update the open help where the other launch bounds are documented.

由索引模型根据 Issue 内容生成。

描述

What happens

openIosSimulatorUrl (packages/platform-apple/src/core/app-launch.ts) runs xcrun simctl openurl <udid> <url> with no timeoutMs. When CoreSimulator is wedged (seen twice on 2026-10-01 under host load 215–691 while working #3096, and once on CI run 36843756495 step 87 where openurl answered NSPOSIXErrorDomain 60 only after its own long internal wait), the open holds until the daemon request timeout (450–630 s in those runs), and the simctl openurl child outlives the daemon's kill of the request.

Every other simctl call the open makes is bounded (listapps, plutil, the terminate calls at 2 s). openurl is the one that can take minutes.

Required behavior

  • simctl openurl runs under a bound of its own, shorter than the open's request budget, and takes the request signal so a cancel kills the child.
  • A timed-out openurl fails the open with a typed reason (dispatched: unknown: the URL may have been delivered) rather than letting the daemon request time out around it.

Completion conditions

  • A unit test with a provider whose openurl never returns: the open fails within the bound with the typed reason, and the child receives the kill.
  • The bound and its reason are documented in the open help where the other launch bounds are.
主要语言
TypeScript
星标
5k
派生
334
平均合并
11 小时 48 分钟
30 天内合并 PR
605

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

callstack/agent-device 的其他 Issue

查看 callstack/agent-device 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。