Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ui: add bar chart for node list memory & capacity #30982

Merged
merged 4 commits into from Oct 5, 2018

Conversation

couchand
Copy link
Contributor

@couchand couchand commented Oct 4, 2018

Adds bar charts to capacity and memory columns on the node list.

new-node-list

Closes #29373

@couchand couchand requested a review from a team as a code owner October 4, 2018 21:01
@vilterp
Copy link
Contributor

vilterp commented Oct 4, 2018

Seeing this in Chrome

image

and this in Firefox

image

Oy.

Copy link
Contributor

@vilterp vilterp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One nit, as well as the FF vs Chrome issue. Otherwise LGTM.

}

render() {
console.log("foobar!");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

stray console.log

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

foobar!

@couchand couchand force-pushed the feature/node-list-updates branch 2 times, most recently from 23d5ee5 to 0cf98d9 Compare October 5, 2018 13:52
Fixes: cockroachdb#29373
Release note (admin ui change): Adds a bar chart to the memory and
capacity usage columns on the node list.
Release note (admin ui change): Sorting by the memory or capacity
usage column on the node list now sorts by percentage used.
Chrome and Firefox have different rules about CSS selectivity
for SVG elements, apparently.  This is a hack, we should find
a simpler way to handle this (maybe changing the conflicting
classes).

Release note: None
@couchand
Copy link
Contributor Author

couchand commented Oct 5, 2018

bors r+

craig bot pushed a commit that referenced this pull request Oct 5, 2018
29623: sql: improve the table name prefix resolution error message r=knz a=knz

Fixes #29594.

Before:

```
root@127.0.0.1:44824/defaultdb> create table t.t(x int);
pq: no schema has been selected to create "t.t" in
HINT: verify that the current database and search_path are valid
```

After:

```
root@127.0.0.1:36392/defaultdb> create table t.t(x int);
pq: cannot create "t.t" because the target database or schema does not exist
HINT: verify that the current database and search_path are valid and/or the target database exists
```

Release note: None

30982: ui: add bar chart for node list memory & capacity r=couchand a=couchand

Adds bar charts to capacity and memory columns on the node list.

![new-node-list](https://user-images.githubusercontent.com/793969/46502317-dccae700-c7f5-11e8-9c02-b3795137f10d.png)

Closes #29373

Co-authored-by: Raphael 'kena' Poss <knz@cockroachlabs.com>
Co-authored-by: Andrew Couch <hi@andrewcou.ch>
@cockroach-teamcity
Copy link
Member

This change is Reviewable

@vilterp
Copy link
Contributor

vilterp commented Oct 5, 2018

Annoyingly, there's still a difference, with spacing — numbers right up against the bar in Chrome; properly spaced in FF:

FF:
image
Chrome:
image

@craig
Copy link
Contributor

craig bot commented Oct 5, 2018

Build succeeded

@craig craig bot merged commit f1b2a73 into cockroachdb:master Oct 5, 2018
@couchand
Copy link
Contributor Author

couchand commented Oct 5, 2018

@vilterp I'm not seeing that in Chrome on Linux, I'll take a look Monday.

@vilterp
Copy link
Contributor

vilterp commented Oct 5, 2018

Hm looking ok now in Chrome…
image
Maybe it was a fluke, or only happens with single digits? Idk.

Overall this is looking really nice!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants