diff options
| author | tv <tv@krebsco.de> | 2026-11-19 20:58:40 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-19 22:10:16 +0100 |
| commit | 59cc0283117be6b4195afbe857d702e7f8ddba6e (patch) | |
| tree | e16ca3aeddb1007eff6b5b289b95a9f562730199 /share | |
| parent | 011560a72ca895d8b516983485cfc45c9984cd45 (diff) | |
continuum-party status: a key, a node, a party a line, nodes by their names
`status` said each party's keys and nodes in one line, separated by
commas, nodes by their IDs alone. Now each goes on a line of its own,
indented beneath its heading (party_lines): the keys the version names,
which sign votes, proposals, the key set and node list; those of the key
set as it counts, which sign writes, or `the same`; `--key`'s marked, and
said where it is none of them; and the nodes, each with the name it gave
itself (`--alias`) where it did, as the dashboard names nodes. The store
and the version are a heading each too, the parties one a line.
The names come from GET /events/counts, which gives each party's
`names` now (by node ID, of the nodes that gave themselves one), so that
a party's session, which reads no /peers, has them. Bash completion
reads the parties from the new layout.
Diffstat (limited to 'share')
| -rw-r--r-- | share/bash-completion/completions/continuum-party | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/share/bash-completion/completions/continuum-party b/share/bash-completion/completions/continuum-party index 057e8a5..de44be7 100644 --- a/share/bash-completion/completions/continuum-party +++ b/share/bash-completion/completions/continuum-party @@ -21,7 +21,7 @@ _continuum_party_proposals() _continuum_party_parties() { _continuum_party_asking status | - sed -n 's/^version .* passing a change (\(.*\))$/\1/p' | tr -d ',' + awk '/passing a change:$/ { on = 1; next } on && /^ [^ ]/ { print $1; next } { on = 0 }' } # The places holding a value. |
