Repository navigation
rdash_sync: stop the board after a pin move so its service restarts on the new checkout - #6
Merged
Merged
Conversation
…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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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/ladderanswered 404 until a hand restart. The sync and the board run as the same user, sofollow_pinnow stops a running board right aftergit submodule update;rdash_service.pysees 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
statussays stopped; a second sync with no board running stops nothing. The fixture now copiesdashboard/supervisoras well, since the server imports it. Full board suite: 272 tests pass.🤖 Generated with Claude Code