0
Fork 0
mirror of https://github.com/zeronsh/comet.git synced 2026-11-16 18:57:19 +00:00
comet/edge/test
Wing 7e1d53000a Cloud: keep zeron-engine, and put it back before each start
New Cloud machines never came online: since 0.3.0 the release's `zeron` is
the zgx app, whose `zeron headless` runs the `zeron-engine` beside it, and
the installer deleted that file (451822be9, when headless linked the
engine). The unit exited at once ("no engine beside …/zeron (zeron-engine)"),
restarted every second, never enrolled, and the chat said "Starting a Cloud
machine…" until the 10-minute limit. 0.3.5's own updater and pre-sleep tidy
leave it out on Cloud too, so a machine updating on a wake broke the same way.

- The installer keeps zeron-engine, and downloads again a version that's
  installed without it.
- A repair (`~/.zeron/repair-engine`) runs before every start of the unit
  (`ExecStartPre=-`, never failing it): with `current` missing zeron-engine,
  it fetches that version's release from the edge and puts the file back.
  The installer sets it up, and so does every wake's first command, so
  machines set up before this get it as they wake (reloading systemd once).

Tested: the install script's unit tier (keeps it, re-downloads a version
without it, the repair restores it and is a no-op once there, a failed
download never fails a start, the wake writes the repair once); the real
0.3.5 release on Linux (restored byte for byte; `zeron headless` then
starts and enrolls); edge unit (100) and Cloud workerd (77) tests.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
History 2026-11-14 20:29:07 -07:00
..
unit Cloud: keep zeron-engine, and put it back before each start 2026-11-14 20:29:07 -07:00
workerd Hosted model list: the engine lays an edge-served list over its built-in catalogs 2026-11-10 08:34:16 -07:00