Slim: nothing optional by default, a lease declares the capabilities it needs
维护者通常 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 内容生成。
描述
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
exceptis today. exceptanddeviceMode: fullbecome 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,通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
callstackincubator/simlock 的其他 Issue
-
request:new
难度 2/5 1-3 小时 新手友好度 72/100
callstackincubator/simlock#1806 ·
维护者通常 1 天内回复
-
bug:new
难度 2/5 1-3 小时 新手友好度 78/100
callstackincubator/simlock#1780 · 1 条评论 ·
维护者通常 1 天内回复
-
task:draft
难度 2/5 1-3 小时 新手友好度 72/100
callstackincubator/simlock#1441 ·
维护者通常 1 天内回复
-
bug:new
难度 2/5 1-3 小时 新手友好度 45/100
callstackincubator/simlock#1805 · 1 条评论 ·
维护者通常 1 天内回复
-
bug:new
难度 2/5 1-3 小时 新手友好度 45/100
callstackincubator/simlock#1804 · 1 条评论 ·
维护者通常 1 天内回复
查看 callstackincubator/simlock 的全部 Issue
相似的 Issue
-
难度 1/5 1 小时以内 新手友好度 82/100
维护者通常 1 天内回复
-
Update project links after the repository renames可能已有人在做 @JonathanTSilva 今天认领。 未关闭ai-generated priority: p2 size: xs type: bug
难度 2/5 1-3 小时 新手友好度 85/100
JonathanTSilva/jts-website#119 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
-
难度 2/5 1-3 小时 新手友好度 74/100
promplate/code-review#158 · 1 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
[Docs] CONTRIBUTING points the Backend Remake milestone at a branch that does not exist可能已有人在做 @franpts2 今天认领。 未关闭docs
难度 1/5 1 小时以内 新手友好度 90/100
维护者通常 3 天内回复