summaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-18 20:10:53 +0000
committertv <tv@krebsco.de>2026-11-18 21:17:46 +0100
commit657765cc512743c248d71b852b4f2e81fa124af7 (patch)
tree546fca8830af331b448786a1d757f41cd56f1232 /docs
parent79614926332977718956f35e1adf80ae67e219f1 (diff)
version: say why a version is none
`Version::read` names what makes a version none: the field it lacks, or the one more it has, that this continuum doesn't know (of the version, a party's keys or node list, a rule), the federation it names beside the one this continuum knows, how many keys or nodes a party has against how many it may, the node ID that is none, and of a key why it is none (`keys::spelled`): its type, its point, or its spelling. A node that stops at a version says so in `stopped` (`GET /events`) and its log; a party's client in what it won't propose or back. The guide to a node that stopped says what `why` tells.
Diffstat (limited to 'docs')
-rw-r--r--docs/guides/federation/when-things-go-wrong.md10
1 files changed, 8 insertions, 2 deletions
diff --git a/docs/guides/federation/when-things-go-wrong.md b/docs/guides/federation/when-things-go-wrong.md
index b59b69b..7c814c2 100644
--- a/docs/guides/federation/when-things-go-wrong.md
+++ b/docs/guides/federation/when-things-go-wrong.md
@@ -75,10 +75,16 @@ nothing by itself or by hand; what is put through it, it still writes into the d
can't judge`), and `GET /events` names the event, why, and how many it holds back:
```sh
-curl -s -u tv:secret localhost:3000/events | jq .stopped
-# {"heldBack":12,"id":"9a1e…","why":"version 3c0f… passed, and doesn't read as one…"}
+curl -s -u tv:secret localhost:3000/events | jq -r .stopped.why
+# version 3c0f… passed, and doesn't read as one here: of federation 2, and this
+# continuum knows 1 alone
```
+`why` says what doesn't read: a federation this continuum doesn't know, a field it
+doesn't know, by its name, a key of a type it doesn't take, or whatever else makes a
+version none ([`proposing-and-voting.md`](proposing-and-voting.md),
+[Writing a version](proposing-and-voting.md#writing-a-version)).
+
Upgrade the node to a continuum that reads it: restarted, it reads its store anew and
takes it. Where none does (two thirds passed a proposal that is no version), have the node
drop that event: it goes on under the version before, refuses the event and any writing