Skip to content
This repository was archived by the owner on Jul 28, 2023. It is now read-only.

Bad config with c.NotebookApp.ResourceUseDisplay... #55

Closed
JonTong opened this issue Feb 24, 2021 · 2 comments · Fixed by #58
Closed

Bad config with c.NotebookApp.ResourceUseDisplay... #55

JonTong opened this issue Feb 24, 2021 · 2 comments · Fixed by #58

Comments

@JonTong
Copy link
Contributor

JonTong commented Feb 24, 2021

On the latest version (jupyter-resource-usage 0.5.1, jupyterlab-topbar 0.6.1 and jupyterlab-system-monitor 0.8.0) running on JupyterLab 3.0.9, I was unable to launch jupyter lab with my jupyter lab config file containing the following:

c = get_config()
c.NotebookApp.ResourceUseDisplay.mem_limit = 4294967296
c.NotebookApp.ResourceUseDisplay.track_cpu_percent = True
c.NotebookApp.ResourceUseDisplay.cpu_limit = 2

Attempting to launch jupyter lab would give the error:
[ ... NotebookApp] Bad config encountered during initialization: Trait, ResourceUseDisplay, not found.

Without these options in my Jupyter config, I was unable to show memory limits or track/show the CPU usage (as expected).

However, changing this to:

c = get_config()
c.ResourceUseDisplay.mem_limit = 4294967296
c.ResourceUseDisplay.track_cpu_percent = True
c.ResourceUseDisplay.cpu_limit = 2

worked and displayed memory limits and CPU usage/limits.

Is this expected? Should the README be changed if so?

@jtpio
Copy link
Owner

jtpio commented Feb 24, 2021

Thanks @JonTong.

It sounds like it's related to this issue: jupyter-server/jupyter-resource-usage#79

It would make sense to also update the docs in this repo for now, before moving the system-monitor extension to jupyter-resource-usage at some point: #51

Would you like to open a PR?

@JonTong
Copy link
Contributor Author

JonTong commented Feb 25, 2021

@jtpio Sure, I'll open a PR.

@jtpio jtpio linked a pull request Mar 1, 2021 that will close this issue
@jtpio jtpio closed this as completed in #58 Mar 1, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants