Public: anyone can read this; the crew can change it.
Migrated from github.com/Trevato/SO-ARM100
A preview deploys while the Pi is offline: GET /healthz answers 200 from the relay alone, and forge.json's health points at it #126
The relay now answers GET /healthz with 200 {"ok":true} and cache-control: no-store. forge.json app.health is /healthz. I couldn't run bun x tsc --noEmit: bun failed with "unable to write files to tempdir: ReadOnlyFileSystem", so the type check hasn't run.
stopped parked by the crew deploy 5192a05
3 earlier comments
The relay now answers GET /healthz with 200 {"ok":true} and cache-control: no-store. forge.json app.health is /healthz. I couldn't run bun x tsc --noEmit: bun failed with "unable to write files to tempdir: ReadOnlyFileSystem", so the type check hasn't run. The relay tests pass (18 of 18). I didn't run the rest of bun --cwd Software/so101 test.
- Route:
/healthzsits next to/linkinSoftware/so101/src/relay.ts. It never contacts the arm, the camera or the simulation. I didn't read the security-header code, so I haven't checked it covers this route. The new test does checkx-content-type-options: nosniffon the response. /status: unchanged. It is still 503 while reconnecting with no last status.- Test: the new test in
src/relay.test.tsstarts a relay pointed at a closed port. It shows/healthzis 200 while/statusis 503. forge.json:healthwas/on this branch, not/statusas the issue says. A later commit had already changed it.
🤖 Generated with Claude Code
The check failed because forge.json had a check block with only limits and no run. I added check.run, which runs the type check and then the tests, and pushed it. I haven't seen the forge's check pass yet.
The command is bun --cwd Software/so101 run typecheck && bun --cwd Software/so101 test. The check block had no run on main either, so the forge would have rejected it there as well.
The type check still doesn't run here, because bun can't write its tempdir in this sandbox. The relay tests passed earlier (18 of 18, including the new /healthz one). I didn't re-run them after this change, since it only touches forge.json.
/healthz on the relay answers 200 {"ok":true} without touching the arm, the camera or the simulation. forge.json app.health now points at it. /status is unchanged and still returns 503 while the arm is unreachable. src/relay.test.ts has a new test that points a relay at a refusing port and checks /healthz is 200 while /status is 503.
🤖 Generated with Claude Code
Declined: this failure comes from main, not from my branch, so I can't fix it by pushing here. Run log: https://forge.open-platform.sh/trevato/arm/runs/01m5e136hpp49kxjwr97z6700h
Parked by the crew: the check stayed red through 2 automatic tries
The relay now answers
GET /healthzwith 200{"ok":true}andcache-control: no-store.forge.jsonapp.healthis/healthz. I couldn't runbun x tsc --noEmit: bun failed with "unable to write files to tempdir: ReadOnlyFileSystem", so the type check hasn't run. The relay tests pass (18 of 18). I didn't run the rest ofbun --cwd Software/so101 test./healthzsits next to/linkinSoftware/so101/src/relay.ts. It never contacts the arm, the camera or the simulation. I didn't read the security-header code, so I haven't checked it covers this route. The new test does checkx-content-type-options: nosniffon the response./status: unchanged. It is still 503 while reconnecting with no last status.src/relay.test.tsstarts a relay pointed at a closed port. It shows/healthzis 200 while/statusis 503.forge.json:healthwas/on this branch, not/statusas the issue says. A later commit had already changed it.🤖 Generated with Claude Code
Closes #120