-
-
Notifications
You must be signed in to change notification settings - Fork 234
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
Update to Jupyterlab 4.0.10 #131
Comments
Nowhere in the generated Dockerfile is I successfully built my own image with jupyterlab 4, simply without jupyterlab-drawio and with the updated spellchecker. jupyterlab-drawio seems no longer to be maintained. The actively maintained |
Hi @kallegrens, I've subscribed to deathbeds/ipydrawio#119 and will build new images if there is a solution or if there won't be any without this package. |
Just wondering if I messed up my image build somehow? Admittedly, I'm pretty new to the 'stacks-based images, not entirely clear on how these images work vs those pulled by vanilla docker-compose, so I probably messed up something basic. |
Hi @mkarikom I will check the Jupyterlab version and also the PyTorch compatibility with CUDA 12.3 (issue #140) and then build a new image with an updated docker-stacks hash. |
Unfortunately, drawio still doesn't support JupyterLab 4.X.
I suggest closing this issue with the support of Juypterlab 4.1, as drawio seems to be not actively maintained at the moment. |
Closing with #144 |
GPU-Jupyter Feature Request
Thank you for your interest in enhancing GPU-Jupyter. We appreciate your ideas and feedback. Please fill out this brief form to help us understand your feature request.
Feature Description
Title
Update to Jupyterlab 4.1
Detailed Description
Benefits
For the same reasons mentioned when deciding to upgrade to Jupyterlab 3.x in #44
Possible Implementation
Additional Information
Screenshots/Illustrations
References
v4.0 changelog
Jupyter blog
We value your contribution and look forward to exploring new features for GPU-Jupyter. Thank you for your support!
The text was updated successfully, but these errors were encountered: