-
Notifications
You must be signed in to change notification settings - Fork 88
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
Unable to configure S3 content manager on recent jupyter-server versions #161
Comments
I suspect this is the main reason: jupyter/notebook#5957 (comment) That got reverted on posterior versions and this package is not ready for that yet. |
Could be yeah. I dont have much time to work on it these days so if you find time to make a PR and update the test matrix it should be easy to test. |
@danielfrg not so proficient in these jupyter world but I found a way to make it work. It turns out that when using If you change them like this it works: -from notebook.services.contents.filecheckpoints import GenericFileCheckpoints
-from notebook.services.contents.filemanager import FileContentsManager
-from notebook.services.contents.manager import ContentsManager
+from jupyter_server.services.contents.filecheckpoints import GenericFileCheckpoints
+from jupyter_server.services.contents.filemanager import FileContentsManager
+from jupyter_server.services.contents.manager import ContentsManager Same applies to HybridContents if used as well, imports have to come from Do you have any recommendation on how to make this less dirty? |
This looks fine to me. If we just wrap that with an if that checks the version of notebook it should work. Its pretty common to do that. |
Another thing I saw was https://github.com/jupyter/nbdime/blob/c82362344e596efdc4f54c927d90338940e0fa41/nbdime/webapp/nb_server_extension.py#L16-L33, which is a bit dirtier |
Yes, its not the cleanest but its pretty common to deal with this situations. |
@danielfrg could you help cut a patch release and publish it on Pypi, thanks! |
Just released |
As for https://discourse.jupyter.org/t/bad-config-encountered-during-initialization-the-contents-manager-class-trait-of-a-singleuserlabapp-instance-expected-a-subclass-of-jupyter-server-services-contents-manager-contentsmanager-not-the-s3contentsmanager-s3contentsmanager/17304, I cannot switch to s3contents as the manager due to getting the same error as above.
My image is based on https://hub.docker.com/layers/jupyter/scipy-notebook/python-3.10.10
I am getting:
Using the following package versions:
Running the following processes on the spawned container:
PS: Note that I had to apply #142 suggestion in order to make it work.
The text was updated successfully, but these errors were encountered: