Without this, as soon as a column is sorted, extra padding is added and
all table contents get shifted a few pixels downwards in a rather jerky
fashion - this is difficult to capture in screenshots. Also, text in
table headers becomes misaligned.
By using sorting symbols that have the same height, sorting columns
asc/desc doesn't make the content in table headers "jump" and remain
misaligned.
This change ensures that nodes whose name begins with `rabbit@` have that leading text removed. This saves UI space as, in production environments, the default node name is `rabbit@`.
While at it, remove remaining references to owner_pid_details.
We don't return it in the API any more.
It is useful for linking to the owner connection, so that part
we will brought back eventually in some shape or form (see #467).
Vhost supervisor status can be different on different nodes.
Report a warning if a vhost is down on any node.
State can be calculated from the cluster state.
Fixes#460
[#149634421]
This is more precise: internal flow control (the "flow"
state) is transient and throttling is a more suitable
and widely used term for describing what it effectively does.
* Don't throw and give up when our "pre-pre-prehistoric virtual DOM"
update isn't consistent, reaload instead
* Coerce the input to a string in two formatting functions
* In the same functions, catch nulls and undefined values early
This fixes a couple of relatively difficult to reproduce exceptions
caused by stats emission timing + DOM updates timing
that make the UI dysfunctional.
It's conventional in GUIs to use a triangle or arrow icon to indicate how
data is currently sorted in a column - where the wide part of the triangle being
at the top and the narrow part at the bottom indicates that larger rows are above
(decreasing sort), and vice versa. In other words, the direction in which the
icon width increases reflects the direction in which the values in the column increase.