A lease cannot require an operator-defined capability, so a closed network cannot be selected like a runner tag
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 55/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- typescript
Línea de trabajo
Start by reading the existing requires handling from issue #513, then trace worker configuration and capability reporting, gateway lease placement, the simlock lease CLI, and the MCP lease schema. Check how CAPABILITY_MISSING is returned when no worker matches. Done means operators can declare custom worker capabilities and leases can require them through the gateway, CLI, and MCP tool.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
The problem
I keep Android emulators on a machine that can reach a bank's closed network, and real phones on a machine that cannot. A test of that network has to land on the first kind of host. Nothing in a lease says which network the worker is on.
lease.request already accepts requires, and a gateway places the lease only on a worker whose status lists each name as available. The names that exist are the four modules Simlock ships: agent-device, input, stream and tunnel. A name I add under capabilities in the worker config is ignored. I cannot declare bank-contour and require it.
--physical, --class and the worker's display label do not carry this. The label is not a routing key.
Who runs into this
A device farm with one Simlock worker inside a closed corporate network and another outside it. Coding agents and CI jobs lease through the same gateway. Today someone has to point each job at the right daemon. A normal lease can be granted on the worker that cannot reach the network under test, and the test then fails for a reason that looks like an app bug.
What you would like to happen
An operator can declare named capabilities on a worker, the way a CI runner has tags. A lease can require one or more of those names and is placed only on a worker that advertises them as available. If none does, the lease fails with the existing CAPABILITY_MISSING instead of being granted on the wrong network.
simlock lease and the MCP lease tool can pass that requirement. Today requires is not a CLI flag, and the MCP lease schema omits it.
Anything else
Seen on simlock 0.5.0, a local worker. Its reported capabilities are agent-device, input, stream and tunnel, all off.
Related, and not the same request:
- #513 added
requiresfor the built-in modules. Its out-of-scope note says no CLI flag and no MCP parameter. - #945 notes that a fleet operator cannot pin a request to a worker or select by label, and that
labelis display-only.
This is not a request to route on the display label. The label is a name. The missing thing is an operator-defined capability that means "this worker is inside the closed network".
A second gap, tags on individual devices of one worker, is filed separately.
Written by an agent.
- 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