generated from amazon-archives/__template_MIT-0
-
Notifications
You must be signed in to change notification settings - Fork 54
LSP script support jump to definition for sagemaker sdk #19
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
Open
seanpmorgan
wants to merge
2
commits into
aws-samples:main
Choose a base branch
from
seanpmorgan:lsp-support-jump-to-definition
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -33,6 +33,16 @@ pip install jupyterlab-lsp \ | |
| # https://jupyterlab-lsp.readthedocs.io/en/latest/Language%20Servers.html | ||
| jlpm add --dev bash-language-server dockerfile-language-server-nodejs | ||
|
|
||
| # Install sagemaker sdk & scikit-learn onto jlab server for source code jump to definition | ||
| pip install sagemaker scikit-learn | ||
| # Create an lsp symlink directory so jupyterlab-lsp can open source-files not found in user home directory | ||
| mkdir .lsp_symlink | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This fails on 2nd run onwards because the folder already exists. When I tried adding the So instead I'm currently testing with: |
||
| ln -s /opt .lsp_symlink/opt | ||
| # Enable opening of symlink files found in the hidden directory `.lsp_symlink/` | ||
| echo yes | jupyter server --generate-config | ||
| sed -i '1i c.ContentsManager.allow_hidden = True' .jupyter/jupyter_server_config.py | ||
|
|
||
|
|
||
| # This configuration override is optional, to make LSP "extra-helpful" by default: | ||
| CMP_CONFIG_DIR=.jupyter/lab/user-settings/@krassowski/jupyterlab-lsp/ | ||
| CMP_CONFIG_FILE=completion.jupyterlab-settings | ||
|
|
||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess difficult to know where to draw the line on what libraries to install for this purpose... Would be ideal if jupyterlab-lsp could properly use the kernel environments instead, but agree demoing sagemaker + one third-party could be a nice compromise to show users what's possible