Slim: nothing optional by default, a lease declares the capabilities it needs

未关闭
#1,688 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
typescript

调研方向

Start by reading ADR 0066 and issue #1650 to understand the current except and ios.slim.include/exclude behavior. Then trace lease resolution and simlock's service categories to assess how capability mappings, defaults, and deviceMode: full would fit. Done means slim devices start with optional services disabled and leases can request capabilities; the issue also leaves open whether agent-device should enable capabilities on demand.

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

描述

request:new

The problem

Slim mode is subtractive: a worker turns off its slim categories, and a lease keeps whole categories back with except (ADR 0066), or individual services through ios.slim.include/exclude (#1650). The caller has to know what simlock turns off and argue against it.

That makes slim conservative in practice. Even with every category on, a slim iOS 26 simulator still runs about 85 system processes (a full one runs about 217), including daemons most UI suites never touch: nanoregistryd/nanoprefsyncd (Watch pairing), routined, geod, mobiletimerd, eventkitsyncd, donotdisturbd, mediaremoted. On a busy Mac, CPU is what limits how many devices a worker can host, so every idle daemon costs capacity.

Proposal: nothing optional by default, a lease asks for what it needs

Turn the model around:

  • A slim device starts with every optional service off: all current categories, plus the single services above.
  • A lease declares what it needs, by capability rather than launchd label, e.g. needs: ["contacts", "location", "notifications", "calendar", "photos", "push", "storekit", "keychain-sharing"]. simlock maps each capability to its labels.
  • An unknown capability is refused at resolve, as except is today.
  • except and deviceMode: full become special cases: full = every capability, except = needs expressed as categories.

Better still: the tool asks for it

agent-device knows when a command needs a service: importing a contact, setting a location, sending a push, opening the photo picker. On the first such command it could ask simlock to switch that capability on for the leased device (launchctl enable + kickstart inside the simulator) and then retry, so suites declare nothing and only what they use ever runs. The capability list is still needed for services that must be up before the app starts.

Why it matters

  • Smaller per-device CPU and memory, so more devices per host.
  • A suite's dependencies become explicit and are reported in the lease record, instead of discovered by a failing test on a slimmer worker.
主要语言
TypeScript
星标
705
派生
40
平均合并
12 小时 9 分钟
30 天内合并 PR
376

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

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

callstackincubator/simlock 的其他 Issue

查看 callstackincubator/simlock 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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