Skip to content

rdash_sync: stop the board after a pin move so its service restarts on the new checkout - #6

Merged
donglaiw merged 1 commit into
mainfrom
sync-restarts-board
Nov 9, 2026
Merged

donglaiw merged 1 commit into
mainfrom
sync-restarts-board

Conversation

@donglaiw

@donglaiw donglaiw commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

Observed on hebb tonight: pytc-jam-msi#7 moved the rdash pin, the minute sync updated the submodule files, but the board process (started 00:52) kept serving the old code, so /plan/ladder answered 404 until a hand restart. The sync and the board run as the same user, so follow_pin now stops a running board right after git submodule update; rdash_service.py sees its health check fail, exits, and systemd (Restart=on-failure) starts the board again from the unit's own environment on the checkout now on disk. About 20 s of downtime, once per pin move.

Test: a real board is started from the fixture, a pin bump is synced, the pidfile is gone and status says stopped; a second sync with no board running stops nothing. The fixture now copies dashboard/supervisor as well, since the server imports it. Full board suite: 272 tests pass.

🤖 Generated with Claude Code

…n the new checkout

A merged pin reached the hebb board's files on 2026-11-09 but the process kept serving
the old code (404 on the new routes) until a hand restart. follow_pin now stops a running
board right after git submodule update; rdash_service.py sees the health check fail and
systemd starts the board again from the unit's own environment. The sync test fixture
copies dashboard/supervisor too, so a board can actually start from it.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@donglaiw
donglaiw merged commit fe745be into main Nov 9, 2026
1 check passed
@donglaiw
donglaiw deleted the sync-restarts-board branch November 9, 2026 06:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant