From f91604095e6f0978c61f66d0b937e36271637e6b Mon Sep 17 00:00:00 2001 From: tv Date: Sun, 8 Nov 2026 17:07:03 +0000 Subject: remake: no --follow-strict-remakes; a strict remake failing says who A strict remake takes a majority of members whose --strict-keys take its manifest's signer: no node votes for one without, so --follow-strict-remakes (1173) goes. A node that doesn't vote still switches once the others commit, as with any remake. So that an operator can tell why one fails: a strict remake aborted for want of a majority (the voting period over, or a majority out of reach) says in its reason (GET /admin/remakes/{id}, and the coordinator's log) which members didn't vote, and that a member votes for one only with its manifest signed by a key of its --strict-keys. Each of those logs why itself (`Not voting for a strict remake`). The sim a_strict_remake_too_few_take: only a takes the manifest; the remake aborts, naming b and c. --- src/main.rs | 1 - 1 file changed, 1 deletion(-) (limited to 'src/main.rs') diff --git a/src/main.rs b/src/main.rs index d0209c0..f632fe9 100644 --- a/src/main.rs +++ b/src/main.rs @@ -265,7 +265,6 @@ async fn main() -> Result<()> { .iter() .filter_map(|line| access::sshsig::PublicKey::parse(line).ok()) .collect(), - follow_strict_remakes: args.follow_strict_remakes, key_logins_per_user: args.key_logins_per_user, cors_origins: args.cors_origins.clone(), files, -- cgit v1.3.1