You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Self-update on systemd never claimed its new version. The dashboard's update wrapper is a child of the very process the restart kills, so the updater died mid-restart and never reached the post-restart version.json commit: the restarted service served the new binary while /health reported the old version, --check kept offering the same update, and update.state stayed running:true. The version claim is now committed before the restart, the previous claim is kept beside it, and a rollback restores it. Sandbox test T12 kills the script at its own restart step and asserts the new claim survived.
The update health check probed the wrong port. The spawn never passed OMNIPROXY_PORT, so update.sh defaulted to 8080 while a prefix install listens elsewhere (20131 on hitokiri): a perfectly good swap would fail the check and roll itself back. The endpoint now passes the configured listen port.