search

aws-samples / sagemaker-studio-lifecycle-config-examples

MIT No Attribution
78 stars 51 forks source link

Language Server Extension latest Sagemaker Studio may lead to failure of lifecycle config #24

Closed jornfranke closed 1 year ago

jornfranke commented 1 year ago

I observe for our lifecycle config - which is not exactly the same as in this project, but similar - that it fails with the following error message:

sagemaker-nb2kg 0.1 requires jupyter-server==2.0.0rc3, but you have jupyter-server 1.23.2 which is incompatible.

sagemaker-nb2kg is an internal extension by Sagemaker Studio (it seems to be in all of them) and jupyter-server 1.23.2 is installed by the lsp extension.

I use

pip install jupyterlab-lsp[all]

I will also test with the exact configuration described here. Maybe someone has come cross this error.

seanpmorgan commented 1 year ago

Thank you for reporting. Will investigate and respond on this thread.

jornfranke commented 1 year ago

in fact the same error occurs with many different jupyterlab extensions on latest Sagemaker Studio with Jupyter 3.x (except the custom Sagemaker Studio cost management extension)

seanpmorgan commented 1 year ago

Apologies for the delayed response on this. The problem was related to jupyter-server release candidate not satisfying extension dependencies. Now that the js2 release is live this should no longer be an issue. Please let us know if you're continuing to see issues.