Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Report the daemon host CPU architecture in /health

Fermée
  • Quelque chose ne va pas ?
#3,047 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
3/5
Temps estimé
1-2 jours
Accessibilité débutants
75/100
Type d'issue
Fonctionnalité
Clarté
Clairement spécifiée
Activité
Active
Stack technique
node.js, typescript
Domaine
api, backend

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
TypeScript
Étoiles
5.1k
Forks
339
Merge moyen
12 h 50 min
PR mergées (30 j)
632

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de callstack/agent-device

Toutes les issues de callstack/agent-device

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.