-
Notifications
You must be signed in to change notification settings - Fork 13
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
status with jupyterlab 4? #65
Comments
I'm also interested in getting support for JupyterLab 4 and JupyterHub 4.1+. I'm testing JupyterLab 4.2.0 + JupyterHub 4.1.5 and the main issue are the more strict requirements on API calls imposed by JupyterHub. Now all calls to non-static resources must be authenticated. This includes all GET calls to the lmod API as well. The internal API calls can be fixed with #66. However, there is one more failure related to the external In theory, replacing |
I started some draft work to make it work with JupyterLab 4 in branch |
Hello, if I understood well what was said in #70 the release 5.2.1 should work with JupyterLab4? I give a try but it seems it isn't. By the way, it seems the tag 5.2.1 isn't set correctly as github says it doesn't exist in this repo. Thanks for all, best |
@ysagon : Can you provide more details what isn't working for you? Both build and execution work fine for me with JupyterLab 4.3.0. The tag 5.2.1 was correctly set, but it was refering to a commit that was yet pushed. It is now fixed. |
Hello @cmd-ntrf : I've tried with JupyterLab/4.0.5 and the lmod icon doesn't appear. I've tried with JupyterLab/4.2.0 and it works, maybe this is a know issue? We are using EasyBuild to built JupyterLab, I just saw they released an update for the same JupyterLab version, maybe this will fix something. I'll let you know. |
I wanted to try this out and added it to our spack build, but it's failing, maybe because it doesn't support jupyterlab 4, or maybe some other dependency is missing? I presume this is something I'm doing wrong, but just wanted to make sure.
The text was updated successfully, but these errors were encountered: