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.

Sign up for GitHub

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

Jump to bottom

Restore nbresuse memory usage indicator on Catalyst pilot hub #143

Closed
zaneselvans opened this issue Dec 17, 2020 · 7 comments · Fixed by #145, #146 or #147
Closed

Restore nbresuse memory usage indicator on Catalyst pilot hub #143

zaneselvans opened this issue Dec 17, 2020 · 7 comments · Fixed by #145, #146 or #147

Comments

@zaneselvans
Copy link
Contributor

For some reason the memory usage indicator from nbresuse that was previously displayed on the Catalyst Cooperative pilot hub seems to have vanished, and I'm also running out of memory (I think, the kernels are dying anyway) while testing our tutorial notebooks, so it would be nice to get it back.

Hopefully we can get our own Docker image building soon.
yuvipanda added a commit that referenced this issue Dec 18, 2020
@yuvipanda
Replace nbresuse with jupyter-resource-usage
127a4f2 
See jupyter-server/jupyter-resource-usage#73

Fixes #143
@yuvipanda yuvipanda mentioned this issue Dec 18, 2020
Merged
@zaneselvans
Copy link
Contributor Author

I shut down my server and logged out, re-authenticated and started up a server and a notebook, but still not seeing any memory usage indicator. I tried installing jupyter-resource-usage on my local machine as well and also didn't get an indicator in my local notebooks so maybe I'm misunderstanding how one gets this information displayed. I didn't see anything related in any of the menu items or plugin manager. Now I'm wondering if this is some kind of jupyterlab 2 vs. 3 issue. Blurgh.

@choldgraf
Copy link
Member

hmmm - let's re-open this one until we can get confirmation that the extension is back and works as-expected 👍

@choldgraf choldgraf reopened this Dec 18, 2020
@zaneselvans
Copy link
Contributor Author

Locally I seem to have both the server and notebook/lab extensions installed and enabled, but still not seeing any output in the JupyterLab interface. Feeling confused. 😕

$ jupyter serverextension list
config dir: /home/zane/miniconda3/envs/pudl-dev/etc/jupyter
    jupyter_resource_usage  enabled 
    - Validating...
      jupyter_resource_usage  OK
    jupyterlab  enabled 
    - Validating...
      jupyterlab 2.2.9 OK
    nbdime  enabled 
    - Validating...
      nbdime 2.1.0 OK
$ jupyter labextension list
JupyterLab v2.2.9
Known labextensions:
   app dir: /home/zane/miniconda3/envs/pudl-dev/share/jupyter/lab
        @axlair/jupyterlab_vim v0.12.4  enabled  OK
        @jupyterlab/toc v4.0.0  enabled  OK
        nbdime-jupyterlab v2.0.1  enabled  OK
$ jupyter nbextension list
Known nbextensions:
  config dir: /home/zane/.jupyter/nbconfig
    notebook section
      vim_binding/vim_binding  enabled 
      - Validating: OK
  config dir: /home/zane/miniconda3/envs/pudl-dev/etc/jupyter/nbconfig
    notebook section
      jupyter_resource_usage/main  enabled 
      - Validating: OK
      nbdime/index  enabled 
      - Validating: OK
      jupyter-js-widgets/extension  enabled 
      - Validating: OK

@yuvipanda yuvipanda reopened this Dec 18, 2020
@yuvipanda yuvipanda mentioned this issue Dec 18, 2020
Merged
@bolliger32
Copy link

Hi everyone - lurking on this thread b/c I came across a similar issue in a totally different hub setting. I believe based on their changelog that you might need to pin to nbresuse 0.3.6 until JupyterLab 3. @yuvipanda you would know better though.

@yuvipanda yuvipanda reopened this Dec 18, 2020
@yuvipanda
Copy link
Member

Hmm, not sure why #146 didn't fix it. I'll look at it tomorrow again :|

@zaneselvans
Copy link
Contributor Author

Well, glad it's not just me that can't get it to show up! Thanks for looking into it.

yuvipanda added a commit that referenced this issue Dec 19, 2020
@yuvipanda
Add dask to our custom image
4066a62 
Issue #143 was caused by changing the catalyst coop image
to the pangeo image, to support dask. However, that doesn't
have nbresuse nor jupyter-resource-usage. Upstream,
pangeo-data/pangeo-docker-images#173 is
working on fixing this.

Catalyst Coop isn't really using dask much, and doesn't need
most of the base libraries that pangeo images provides. So we
add dask to our base image, and use that instead.
@yuvipanda yuvipanda mentioned this issue Dec 19, 2020
Merged
@yuvipanda
Copy link
Member

I think #147 fixed this - I can see the indicator now.

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
4 participants
@yuvipanda @zaneselvans @choldgraf @bolliger32