Repository navigation
update restarts a stale hub; doctor says where to update it; clearer desktop notes docs - #105
Merged
Merged
Conversation
gaius-codius
changed the title
Merged
gaius-codius
added a commit
that referenced
this pull request
Oct 25, 2026
Release v0.8.1: the changelog's Unreleased section becomes 0.8.1, and plugin.json's version is 0.8.1. It holds #105: `ostrakon update` restarts a hub left on an older release, `doctor` says where to update the hub, and clearer desktop-notes docs.
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.
The hub on this machine ran 0.6.0 while its checkout was on 0.8.0: the checkout had been pulled without
ostrakon update, so the service never restarted.doctorsaid "run ostrakon update where the hub runs", butupdatefound nothing to pull and stopped before the hub.What changed
update.sh(ostrakon update) restarts the hub on this machine after new code, as before, and now also when the hub's/healthzreports a different release from the checkout's. It reads the port from the service'sHUB_PORT(default 8790).ostrakon doctor, when the hub runs a different release: if that's the hub on this machine (the service is active and its/healthzreports the same version), it saysostrakon updaterestarts it. Otherwise it names the hub's host: "on , run ostrakon update".Checked
shellcheckon both scripts.doctorwith the checkout's version set to 0.8.9: "the hub on this machine runs 0.8.0, this checkout 0.8.9; ostrakon update restarts it". The host is taken fromhttps://box.tail1.ts.net:8443,http://10.0.0.5:8790/andhttps://hub.example.com/x.update.shin a scratch clone of main: with a local commit setting the version to 0.8.9, it says "already up to date", "the hub runs 0.8.0, this checkout 0.8.9", "hub restarted", and the service's start time moved. With the versions matching, it says "already up to date" and leaves the hub alone.