From 7404dcef34dbad11a5ac2a6b8a27836b01c82635 Mon Sep 17 00:00:00 2001 From: tv Date: Wed, 18 Nov 2026 20:12:04 +0000 Subject: events: why no party's client backs a proposal `GET /events/counts` gives each proposal on the current version `none`: why a party's client backs it not (`client::backable`), where it is no version as this node reads it, none changing the current one, or one naming the heads of the current one's checkpoint; else `null`. So a node shows that a proposal is none, and why, before it passes: one that passes all the same is never written, or, no version here, the node stops at its version event. The dashboard shows it with the proposal, and `continuum-party proposals` says it by the federation the client knows. Row 48's test checks what a node shows of the proposal. --- src/federation/party.rs | 3 +++ 1 file changed, 3 insertions(+) (limited to 'src/federation/party.rs') diff --git a/src/federation/party.rs b/src/federation/party.rs index 60b7e18..04837c3 100644 --- a/src/federation/party.rs +++ b/src/federation/party.rs @@ -807,6 +807,9 @@ async fn proposals(node: &Node) -> Result<()> { does: Does::Proposal { hash: of, version }, .. })) if of.to_string() == *hash => { + if let Err(why) = client::backable(¤t, &version) { + println!(" backed by no client: {why}"); + } for line in client::changes(¤t.json, &version) { println!(" {line}"); } -- cgit v1.3.1