A lease cannot require an operator-defined capability, so a closed network cannot be selected like a runner tag

オープン
#1,541 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
55/100
issue の種類
機能追加
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
typescript
領域
api, backend, cli

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

request:new
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 requires for 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 label is 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.

主要言語
TypeScript
スター
705
フォーク
40
平均マージ
12時間 9分
マージ済み PR(30日)
376

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

callstackincubator/simlock のほかの issue

callstackincubator/simlock の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。