-
Notifications
You must be signed in to change notification settings - Fork 56
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
Jupyterlab Code Formatter Error in AWS SageMaker Studio #334
Comments
Did you find any solution? I am getting the same error |
No, unfortunately not. Still the same problem on my side. |
I am surprised that no one else has this problem / care about this |
We had the same issue which got resolved after jupyter server restart using "/usr/local/bin/restart-jupyter-server" command. |
Here's a more complete setup provided by SageMaker team: https://github.com/aws-samples/sagemaker-studio-lifecycle-config-examples/blob/main/scripts/install-lsp-features/on-jupyter-server-start.sh#L73-L75 In short, you're missing |
Environment
Issue Description
When attempting to format Python code using the
jupyterlab-code-formatter
extension within JupyterLab on AWS SageMaker Studio, the formatting action fails and triggers a "Jupyterlab Code Formatter Error, Not Found" error message. This occurs despite the extension appearing as enabled and properly validated within my environment.Steps to Reproduce
jupyterlab-code-formatter
version 2.2.1, along withblack
andisort
.jupyter server extension list
.jupyterlab-code-formatter
icon.Additional Context
pip list
output: (Included key packages relevant to formatting)black 24.3.0
isort 5.13.2
jupyterlab 4.1.5
jupyterlab_code_formatter 2.2.1
jupyter server extension list
output:jupyter_lsp 2.2.4 OK
jupyter_server_terminals 0.5.3 OK
jupyterlab 4.1.5 OK
jupyterlab_code_formatter 2.2.1 OK
notebook_shim OK
CloudWatch log entry on format action:
Despite the extensions being recognized and validated by the server, the formatting request fails. Notably, the environment and installation details have been double-checked for consistency and correctness.
Any guidance on troubleshooting or resolving this issue would be greatly appreciated.
Thanks a lot for your help :)
The text was updated successfully, but these errors were encountered: