Skip to content

Report which hotcell-server version a cell runs in its describe response - #73

Merged
flavorjones merged 1 commit into
masterfrom
issue-21-describe-server-version
Sep 29, 2026
Merged

flavorjones merged 1 commit into
masterfrom
issue-21-describe-server-version

Conversation

@flavorjones

Copy link
Copy Markdown
Member

Motivation

hotcell.describe is the request a cell answers on its control socket to say what it carries. The client sends it at app boot (HotCell.describe_cells), and operators poll it from a health endpoint. Its answer (control.rb) holds v, the operations, the groups, and the configuration.

v is the protocol version, the wire format. It is 1 and changes only when the format does. So two cells running different releases give the same answer, and an operator cannot tell which hotcell-server release a deployed cell runs without shelling into the container.

Part of #21

Details

  • The describe answer now includes server_version, the HotCell::Server::VERSION of the cell.
  • A new test in control_test.rb boots a cell and checks the value it reports.
  • The client does not read the new key. An older client ignores it, and a newer client still reads an older cell.

A cell's `hotcell.describe` answer carried only the protocol version,
which stays at 1 across releases, so nothing in it said which
`hotcell-server` release the cell ran.

Add `server_version`, the cell's `HotCell::Server::VERSION`.

ref: #21
Copilot AI balanced review requested due to automatic review settings September 28, 2026 21:24

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@flavorjones
flavorjones merged commit c8e10ac into master Sep 29, 2026
16 checks passed
@flavorjones
flavorjones deleted the issue-21-describe-server-version branch September 29, 2026 16:34
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.

2 participants