Scott Dickerson

> @sgratch > From what I found it seems like the issue is permissions/REST issue and cannot be fixed from the web UI. > I queried the REST using REST...

:exclamation: **Note** :exclamation: - PR #1592 was reverted (#1604) and as such this PR is no longer valid / relevant.

Closing the PR since this change was based on #1592, and that change was reverted by #1604, this PR is no longer valid.

Note: This should be current behavior since pool redesign (#195, #990) has been merged.

@michalskrivanek , @sgratch , @rszwajko , @hstastna - Thoughts and comments?

Good article about dockerizing react app https://mherman.org/blog/dockerizing-a-react-app/ It isn't 100% applicable (missing the user login from ENV vars, missing the api proxy), but would be a good base.

**Note**: travis-ci.org is shutdown as of June 15.

After looking at it a bit, I'd say that `GlobalErrorBoundary` itself keeps all the error trapping as-is. Then the refactoring would be to take out the `render()` function and spin...

> After looking at it a bit, I'd say that `GlobalErrorBoundary` itself keeps all the error trapping as-is. > > Then the refactoring would be to take out the `render()`...

The historic statistics from the REST API do not include timestamps with the data points. So apart from those datapoints somehow being tied to the current date/time (the first data...