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
Owner

For inbuxa/inbuxa-server#485.

The dashboard's Needs attention rail gets a critical item, N listeners not open, naming each node, listener, address and reason, from x:ClusterNode.unboundListeners. It shows on a single server too, where the cluster card doesn't, and links to the cluster page when there is one.

The node fetch no longer names properties: naming unboundListeners would fail on a server without it and take the cluster card with it. A registry set arrives as {"<value>": true}, so the lines are read from the keys (setOf).

Checked: typecheck, lint, i18n (2 new strings), all tests (1152, four new), build, notice check. Live: server with port 12993 held, signed in, the rail showed "1 listener not open · bench: imaps [::]:12993: Failed to bind ... Address already in use (os error 98); retrying".

Merge with inbuxa/inbuxa-server#487.

For inbuxa/inbuxa-server#485. The dashboard's **Needs attention** rail gets a critical item, **N listeners not open**, naming each node, listener, address and reason, from `x:ClusterNode.unboundListeners`. It shows on a single server too, where the cluster card doesn't, and links to the cluster page when there is one. The node fetch no longer names properties: naming `unboundListeners` would fail on a server without it and take the cluster card with it. A registry set arrives as `{"<value>": true}`, so the lines are read from the keys (`setOf`). **Checked:** typecheck, lint, i18n (2 new strings), all tests (1152, four new), build, notice check. Live: server with port 12993 held, signed in, the rail showed "1 listener not open · bench: imaps [::]:12993: Failed to bind ... Address already in use (os error 98); retrying". Merge with inbuxa/inbuxa-server#487.
jcoffey-dev added 2 commits 2026-11-19 17:25:35 +00:00
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.
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
b677d473ce
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.
jcoffey-dev merged commit 2ca76415fe into main 2026-11-19 17:52:20 +00:00
jcoffey-dev deleted branch feat/485-unbound-listeners 2026-11-19 17:52:20 +00:00
Sign in to join this conversation.