ui: Raft ranges debug page shouldn't auto-refresh #21700
Assignees
Labels
S-3-ux-surprise
Issue leaves users wondering whether CRDB is behaving properly. Likely to hurt reputation/adoption.
Milestone
Comments
couchand
added
the
S-3-ux-surprise
mrtracy
pushed a commit
to mrtracy/cockroach
that referenced
this issue
Mar 5, 2018
Two debug pages (Localities and Raft Ranges) were flashing content while refreshing data; this is because they were using the wrong criteria for determing whether to display a "loading..." message instead of content. Fixes cockroachdb#23411 Fixes cockroachdb#21700 Release note: None
mrtracy
pushed a commit
to mrtracy/cockroach
that referenced
this issue
Mar 6, 2018
Two debug pages (Localities and Raft Ranges) were flashing content while refreshing data; this is because they were using the wrong criteria for determing whether to display a "loading..." message instead of content. Fixes cockroachdb#23411 Fixes cockroachdb#21700 Release note: None
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
/#/raft/rangespage is really cool -- it was a great reference yesterday while reproducing/debugging #20241. However, it was very tough to use because it auto-refreshes every few seconds, replacing the great content with a "Loading..." message and then scrolling you back up to the top instead of keeping your place when the new content loads. I see no reason for this page to need to auto-refresh, but if for some reason we need to keep the auto-refresh then it at least shouldn't scroll you back up to the top of the page when it does so.@BramGruneir
The text was updated successfully, but these errors were encountered: