Skip to content

cut: drop the add-node response's usage - #750

Merged
CMGS merged 1 commit into
masterfrom
cut/add-node-usage
Sep 9, 2026
Merged

CMGS merged 1 commit into
masterfrom
cut/add-node-usage

Conversation

@CMGS

@CMGS CMGS commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

What

AddNodeResponse loses its Usage field; cpumem stops filling it.

Why

The field came with the 2023 plugin protocol as the pair of capacity, but cobalt reads only the capacity of a fresh node (resource/cobalt/node.go), calcium stores only that, and nothing ever sent a usage other than zero. A binary plugin that still emits usage is decoded without it, so plugin binaries built before this change keep working; resource-extend's matching PR stops sending it.

Evidence

Gate on the branch: build, vet, full tests, make lint, make fmt-check and asl on both GOOS green; comment delta +0 −0; production −4.

The field came with the 2023 plugin protocol as the pair of capacity,
but cobalt reads only the capacity of a fresh node and nothing ever
sent a usage other than zero. A binary plugin that still emits it is
decoded without it.
@CMGS
CMGS merged commit e19ceb7 into master Sep 9, 2026
5 of 7 checks passed
@CMGS
CMGS deleted the cut/add-node-usage branch September 9, 2026 10:04
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