Public: anyone can read this; the crew can change it.
Migrated from github.com/Trevato/SO-ARM100
Exactly one STOP on every layout: red, >= 56 px, fires on pointerdown, resume asks for a second tap, a full-width stopped banner #104
This closes the two gaps left in #91. I did not add the Playwright viewport test, so that done-item is still open. I didn't run the app in a browser at any viewport.
stopped parked by the crew deploy 84a2a00
2 earlier comments
This closes the two gaps left in #91. I did not add the Playwright viewport test, so that done-item is still open. I didn't run the app in a browser at any viewport.
main already had the other parts. There is one [data-stop] button, it fires on pointerdown, and resume asks for a second tap.
- Size: the STOP button's minimum height goes from 52 px to 56 px (
Software/so101/src/viewer.html). It was already red. - Banner: the stopped banner (
#banner.stop) now spans the full width of the screen. It used to be a centred box sized to its text. - Tests:
src/server.test.tsnow also checks the 56 px red button, the full-width banner and thepointerdownhandler. The existing one-button check stays. - Why no Playwright: the repo has no Playwright dependency and no browser test. Browser tests are what died at the old step limits, and adding one needs a new dependency. It is better as its own issue.
- Test results:
stop.test.tspasses, and the type check printed no errors.server.test.tshas one failure, "serves the model, its meshes and the vendored libraries". It fails identically without my change, because the vendored model files aren't installed in this sandbox. Bun also reported it could not write to its temp directory.
The preview deploy failed because its health check got a 503, not because of the STOP change. I've pointed the health check at an endpoint that stays up and pushed. I haven't seen the new deploy or the check run, so I don't know yet whether it passes.
- Cause:
forge.jsonhealth-checked/status, which returns 503 while the app can't reach the real arm (100.89.95.68:8101). The preview couldn't reach it, so the page was up but the deploy was marked failed after 30 s. I reproduced the 503 locally with the arm unreachable. The earlier parked deploy failure for #91 probably had the same cause. - Fix:
forge.jsonnow health-checks/link. It returns 200 while the arm link is down and reports thereconnectingmode. - Checks run:
manifest.test.tspasses, and the earlier STOP tests were unaffected. - Check state: when I looked, the check on #104 was still queued, not failed. The failing run was the deploy.
The health check now only says the server is up, not that the arm is reachable. The page and /status still show the reconnecting state to drivers. A person should confirm they're happy with that trade for production health.
Parked by the crew: the check stayed red through 2 automatic tries
This closes the two gaps left in #91. I did not add the Playwright viewport test, so that done-item is still open. I didn't run the app in a browser at any viewport.
mainalready had the other parts. There is one[data-stop]button, it fires onpointerdown, and resume asks for a second tap.Software/so101/src/viewer.html). It was already red.#banner.stop) now spans the full width of the screen. It used to be a centred box sized to its text.src/server.test.tsnow also checks the 56 px red button, the full-width banner and thepointerdownhandler. The existing one-button check stays.stop.test.tspasses, and the type check printed no errors.server.test.tshas one failure, "serves the model, its meshes and the vendored libraries". It fails identically without my change, because the vendored model files aren't installed in this sandbox. Bun also reported it could not write to its temp directory.Closes #91