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/fold.rs | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'src/federation/fold.rs') diff --git a/src/federation/fold.rs b/src/federation/fold.rs index fddedc0..3ebeebf 100644 --- a/src/federation/fold.rs +++ b/src/federation/fold.rs @@ -341,6 +341,12 @@ impl State { ballots } + /// The version the proposal of hash `proposal` proposes, as JSON, where it holds one: + /// whether it is a version is asked apart (`Version::read`). + pub(crate) fn proposal(&self, proposal: &Id) -> Option<&Json> { + self.proposed.get(proposal) + } + /// The version event writing the proposal of hash `proposal` on the current version, /// where it passed here: on the `true` votes of the first parties by name that pass it, /// each party's of the lowest ID, so that nodes holding those votes write the same. -- cgit v1.3.1