-
-
Notifications
You must be signed in to change notification settings - Fork 498
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
Automatic vscode detection is not always working #5200
Labels
type: enhancement
Minor feature or improvement to an existing feature
Comments
@giladpn, Is it possible for you to run the above code in a notebook running in a docker container? |
@hoxbro Done. I ran this on a docker RHEL9 container: |
Would propose we check for VSCODE_CWD in addition to VSCODE_PID |
What about warning if jupyter_bokeh not installed? |
Unrelated to this issue. See your own issue here #5190 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Continuation of #5007.
When running VSCode inside a virtualization/containerized environment, for example, WSL on Windows, the system environment variable we use
VSCODE_PID
to detect if we are running inside a vs code notebook is not set. Below is an example of theVSCODE_
environment variables set in a notebook environment on WSL.The text was updated successfully, but these errors were encountered: