Worker: an admission command that ranks or refuses local lease requests (ADR 0074 on the worker)
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 35/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- typescript
Línea de trabajo
Start with ADR 0074 and src/leasing/acquisition-admission.ts, then trace how gateway admission commands receive requests and how local worker lease requests are stored. The proposal also points to worker configuration and status reporting as entry points. Done means local requests support operator admission and fail closed if the controller stops, while existing leases and in-flight operations follow the stated use case.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Problem
ADR 0074 lets a gateway run an operator admission command that ranks or refuses each new lease.request. On a host that runs a worker, though, local agents lease from the worker directly. So an operator who must hold the host's simulators for a scheduled workload (a CI train, a measurement run, maintenance) has no supported way to refuse new local provisioning.
Verified against v0.8.0:
- docs
reference/cli.mdx"Which daemon a command reaches": with neither--gatewaynor--local, a command goes to the gateway only when no worker has started on the machine. So on a worker host the default CLI and MCP reach the worker. gateway/joining-workers.mdx: "Agents on the worker machine still lease devices from it directly."gateway/access-control.mdx: on the daemon's own machine the CLI needs no token.- source
src/leasing/acquisition-admission.tsholds only internal checks (requester limit, lease ids). There is no operator hook on the worker. worker drainexists only for gateways. On a standalone worker, capacity limits apply only at daemon start.
Context: the same shared-Mac setup as #1587 / #1737 (one Mac mini, one worker, ~10 concurrent coding agents, plus scheduled CI trains on the same host).
Use case
Before a train starts, the operator needs to:
- refuse new simulator/emulator provisioning (new leases, boots, installs);
- let boots already in flight finish and keep existing leases (no forced release);
- admit only the train's own requests while it runs (by request
metadata); - stop refusing when the train ends.
Hard requirement: fail closed if the controller dies. If the process that holds the reservation is killed or interrupted, new provisioning must stay refused until an operator or the controller clears it. It must never fall back to admitting.
Proposal
Mirror ADR 0074 on the worker:
admission.command(an argv list) andadmission.timeoutMsin the worker config. The command runs once per new locallease.request, after the cheap refusals and before the request is stored. The stdin/stdout contract is the same as the gateway's ({}/{"priority": n}/{"deny": "reason"}), it receives the caller'smetadata, and it fails closed withADMISSION_FAILED.- Requests relayed by a gateway that already ran its own command can skip the worker's command (configurable).
- Optional simpler switch:
worker drainon a standalone worker (refuse new local leases, keep existing ones). - Status exposes in-flight lifecycle operations (booting/creating/installing), so a controller can wait for them to settle before it takes ownership.
Alternatives considered
- A same-host gateway with an admission command: local agents bypass it (see above).
- Running the worker from a separate
SIMLOCK_HOMEso the default CLI resolves to the gateway: possible, but it relocates device state and puts a gateway hop on every localsimctl/adb/install. - Restarting the daemon with lower capacity limits: needs 0 leases and a restart each time.
Environment: Simlock 0.5.0 (planning 0.8.0), macOS 27.2, Xcode 27.2, single-host worker.
- Lenguaje dominante
- TypeScript
- Estrellas
- 705
- Forks
- 40
- Merge medio
- 12 h 9 min
- PR fusionados (30 d)
- 376
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de callstackincubator/simlock
-
request:new
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
callstackincubator/simlock#1806 ·
Los mantenedores suelen responder en 1 día
-
bug:new
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
callstackincubator/simlock#1780 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
task:draft
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
callstackincubator/simlock#1441 ·
Los mantenedores suelen responder en 1 día
-
bug:new
Dificultad 2/5 1-3 horas Aptitud para principiantes 45/100
callstackincubator/simlock#1805 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
bug:new
Dificultad 2/5 1-3 horas Aptitud para principiantes 45/100
callstackincubator/simlock#1804 · 1 comentario ·
Los mantenedores suelen responder en 1 día
Todos los issues de callstackincubator/simlock
Issues similares
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día
-
Update project links after the repository renamesPosiblemente ocupada @JonathanTSilva la tomó hoy. Abiertoai-generated priority: p2 size: xs type: bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
JonathanTSilva/jts-website#119 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
promplate/code-review#158 · 1 comentario · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
[Docs] CONTRIBUTING points the Backend Remake milestone at a branch that does not existPosiblemente ocupada @franpts2 la tomó hoy. Abiertodocs
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
Los mantenedores suelen responder en 3 días