-
Notifications
You must be signed in to change notification settings - Fork 78
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
Managing Lifecycle of nvdashboard #63
Comments
Thanks for raising this. Could you share how you are starting the extension? Via Jupyter Lab or standalone? |
The extension is automatically started as part of RAPIDS NGC Container. So I assume within the container it is initiated with the jupyter lab. |
Ok thanks. Do you have thoughts on what the most natural feeling way to restart and reconfigure would be? |
From a user experience point of view, a terminal command to restart nvdashboard (and an argument that specifies the new port) that can be executed inside the container where jupyter lab is running, would be great. |
Currently there is no way to close an existing nvdashboard process. I have tried multiple ways to close the process but it starts back up again automatically. I believe it is because of ioloop module by Tornado web server.
Please include a safe way to:
This will help manage nvdashboard server lifecycle in an independent way (as opposed to being tied to a default port).
The text was updated successfully, but these errors were encountered: