Dashboard: listeners a node couldn't open #252

Merged
jcoffey-dev merged 2 commits from feat/485-unbound-listeners into main 2026-11-19 17:52:20 +00:00
2 Commits
Author SHA1 Message Date
jcoffey-dev b677d473ce Dashboard: read a node's unbound listeners as the set the server sends
ci / build (pull_request) Skipped
ci / publish (pull_request) Skipped
ci / notices (pull_request) Successful in 58s
github/ci (branch) GitHub Actions
ci / github (pull_request) Successful in 2m35s
A registry set arrives as {"<value>": true}, so the listener lines are
the keys; reading the values showed "true". Found against a live server
holding a port; the test uses the string it sent.
2026-11-19 10:25:01 -07:00
jcoffey-dev c19b29bb87 Dashboard: listeners a node couldn't open (inbuxa-server#485)
Each x:ClusterNode now says which of its listeners it couldn't open. The
attention rail shows them as one critical item, "N listeners not open",
naming the node, the listener, its address and why, and linking to the
cluster page. It shows on a single server too, where the cluster card
doesn't.

The node fetch no longer names the properties it wants: naming
unboundListeners would fail against a server without it, and the cluster
card would go with it.

Test: unboundOf (inactive leases left out, single server included) and
the attention item.
2026-11-19 10:17:56 -07:00