From 171f1fcabcdb62b93696f5028120e9d5390b118a Mon Sep 17 00:00:00 2001 From: tv Date: Tue, 17 Nov 2026 04:10:55 +0000 Subject: remake: holding a store, a node puts again what the document it left holds After a switch or a rejoin, a node of a swarm holding a store puts again what the document it left holds that a store starting at the new document's checkpoint takes, by its own refusals and drops, and the new one lacks (`docs/store.md`, Remakes, `Holding::left`): what it held beyond the base, and, where it moved to a later checkpoint since, what a store starting at the snapshot's takes to reach it. Its events aren't replayed into the new document, so none nobody takes go along. --- src/remake/switch.rs | 11 +++++++++++ 1 file changed, 11 insertions(+) (limited to 'src/remake/switch.rs') diff --git a/src/remake/switch.rs b/src/remake/switch.rs index 94956f6..657b0f5 100644 --- a/src/remake/switch.rs +++ b/src/remake/switch.rs @@ -297,6 +297,17 @@ async fn switch( &old, std::mem::take(&mut stats.quarantined), ); + // Holding a store: what the old document holds that the new one's store takes goes + // again (`Holding::left`). + #[cfg(feature = "federation")] + let old = { + let holding = host.holding(); + host.read_doc(move |doc| { + holding.left(doc, &old); + old + }) + .await + }; host.remake().archive( previous, old, -- cgit v1.3.1