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".
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.
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.
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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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
unboundListenerswould 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.
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.