aboutsummaryrefslogtreecommitdiffstats
path: root/src/remake/mod.rs
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-17 04:16:59 +0000
committertv <tv@krebsco.de>2026-11-17 05:33:18 +0100
commit5439b2e6b27a55a1da252cf745d0557686e9c815 (patch)
tree2b26c192e22e1b130a2ca7674fc1713e94fa59f7 /src/remake/mod.rs
parent44a61c46160843d917a1da24bc8e364c5109960d (diff)
remake: holding a store, a node follows an epoch only from a checkpoint it builds
A node of a swarm holding a store rejoining an epoch (`docs/store.md`, Remakes) follows it only where its snapshot has the swarm's policy and store, and holds the node's document's checkpoint, one it builds from that document, or one its operator pinned; with an empty document, the root of its store too (`Holding::follows`). A made-up epoch holding another, the root after the store moved on, say, would leave it holding events whose history nobody puts again: it stays on its own, as when a rejoin's check fails, and tries again later.
Diffstat (limited to 'src/remake/mod.rs')
-rw-r--r--src/remake/mod.rs5
1 files changed, 5 insertions, 0 deletions
diff --git a/src/remake/mod.rs b/src/remake/mod.rs
index bd814da..1f7a644 100644
--- a/src/remake/mod.rs
+++ b/src/remake/mod.rs
@@ -217,6 +217,11 @@ pub(crate) trait Host: Clone + Send + Sync + 'static {
#[cfg(feature = "federation")]
fn holding(&self) -> Arc<crate::federation::held::Holding>;
+ /// The store this node's swarm holds, as its operator named it (`--store-id`,
+ /// `--store-root`), if any.
+ #[cfg(feature = "federation")]
+ fn store_id(&self) -> Option<crate::federation::store::Id>;
+
/// The epoch of the local replica.
fn current_epoch(&self) -> Epoch;