From c64fcc05d8c53bee99ab039bd709039afb730cdd Mon Sep 17 00:00:00 2001 From: tv Date: Wed, 18 Nov 2026 18:49:50 +0000 Subject: federation: a node stops at a version it doesn't read A version event writing a proposal passed on the version a node reads, which doesn't read as a version there (of a later federation, using what a later continuum takes, or none at all), the node can't judge: `Fold::stops`. The store stops at it: it takes nothing and refuses nothing from then on, holding back whatever comes, that event first (`Offered::Stopped`), and keeps none of it across a restart, where it stops there again. One beside the version the node reads is refused of its own, as any other. Its operator has it drop that event (`POST /admin/events/drop`), or one it builds on: it is refused as dropped, or as built on what was, any version event writing that version with it, kept in the store file; the node judges what it held back and goes on under the version before. Allowed again, it stops there once more. The node logs the stop and its end; `GET /events` names the event, why, and how many it holds back (`stopped`); a put answers `stopped`, written into the document all the same; a node voting by itself casts nothing while stopped. The test fold's eras tagged `new` stop a store. Row 39 is tested (`federation_attack_39`); of rows 9, 10 and 48, a node stops at the version event. --- docs/guides/federation/refusals-and-drops.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) (limited to 'docs/guides/federation/refusals-and-drops.md') diff --git a/docs/guides/federation/refusals-and-drops.md b/docs/guides/federation/refusals-and-drops.md index b32a819..1d29df1 100644 --- a/docs/guides/federation/refusals-and-drops.md +++ b/docs/guides/federation/refusals-and-drops.md @@ -40,8 +40,9 @@ file`). ## Dropping -An operator may have the node drop events it took after its checkpoint, with everything -built on them: +An operator may have the node drop events it took after its checkpoint, or the version +event it stopped at ([`when-things-go-wrong.md`](when-things-go-wrong.md), +[A node stopped](when-things-go-wrong.md#a-node-stopped)), with everything built on them: ```sh curl -u tv:secret -X POST -H 'Content-Type: application/json' \ @@ -50,7 +51,8 @@ curl -u tv:secret -X POST -H 'Content-Type: application/json' \ ``` It answers what it dropped, in the order taken: those named, version events naming the -version one of them names, and what is built on them. From then on the node refuses those +version one of them names, and what is built on them; then the event it stopped at, if +named, after which it takes again. From then on the node refuses those events from whoever brings them, and any version event naming a version among them, whoever wrote it anew; it writes none itself, though it holds the votes passing it, and keeps so across restarts. Not what its checkpoint keeps -- cgit v1.3.1