Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Report the daemon host CPU architecture in /health

オープン
  • 何か問題がありますか？
#3,047 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

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

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

評価

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

調査の方向性

Start at the existing /health handlers for the daemon and proxy, then trace how the proxy includes upstream health and how readRemoteDaemonHealth parses the response. Check the existing resolveMacRunnerArch behavior for architecture naming. Done means hostArch is reported and forwarded as specified, absent fields still parse, and the protocol check remains unchanged.

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

説明

Purpose

A remote client cannot learn the CPU architecture of the host its simulators run on. Nothing in /health, devices --json, or eas simulator:get reports it.

Stim (appandflow/stim#1803) builds iOS simulator apps on one machine and installs them on a remote Mac's simulator through agent-device proxy or an EAS Simulator session. xcodebuild has no remote UDID at build time, so the build uses generic/platform=iOS Simulator, which forces ONLY_ACTIVE_ARCH=NO and compiles both arm64 and x86_64. On an Expo app that measured 285 s and a 341 MB .app, against 151 s and 172 MB with ARCHS=arm64. Knowing the host arch lets the client build one slice.

Observed on a real EAS Simulator session (daemon 0.21.16, client 0.21.12):

{"ok":true,"service":"agent-device-daemon","version":"0.21.16","rpcProtocolVersion":2}

agent-device devices --platform ios --json lists platform, appleOs, id, name, kind, target, booted, with no arch.

Required behavior

/health advertises an optional hostArch for the process that serves it, normalized to Apple arch names: Node x64 becomes x86_64, arm64 stays arm64, other values pass through. A proxy reports its own hostArch and the upstream daemon's inside upstream, as it already does for version.

{"ok":true,"service":"agent-device-proxy","version":"0.21.17","rpcProtocolVersion":2,"hostArch":"arm64",
 "upstream":{"ok":true,"service":"agent-device-daemon","version":"0.21.17","rpcProtocolVersion":2,"hostArch":"arm64"}}

The field is additive under ADR 0006 (a new optional response field older clients ignore), so rpcProtocolVersion stays 2. readRemoteDaemonHealth parses it when present and tolerates its absence.

Health is the right surface rather than device entries: arch is a property of the host, simctl does not report it per simulator, and a per-device field would cross discovery, the client normalizer, the output serializer and the MCP schema.

Known limit: the value is the arch the daemon's Node process runs as. An x64 Node under Rosetta on Apple silicon reports x86_64 while simulators boot arm64. resolveMacRunnerArch makes the same trade for the macOS runner destination.

Completion

  • curl <daemon>/health on an Apple silicon Mac includes "hostArch":"arm64".
  • Through agent-device proxy, both the proxy payload and upstream carry it.
  • A health payload without the field still parses, and the client's protocol check is unchanged.

Environment: macOS 27.0, Xcode 27.0, Node 22.22.2.

主要言語
TypeScript
スター
4.7k
フォーク
304
平均マージ
11時間 6分
マージ済み PR（30日）
521

環境構築

はじめの一歩

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

callstack/agent-device のほかの issue

callstack/agent-device の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

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

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