Skip to content
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

Jupyter interpreter can be invalid and break things #1110

Closed
Tracked by #11092
rchiodo opened this issue Nov 13, 2020 · 5 comments · Fixed by #11109
Closed
Tracked by #11092

Jupyter interpreter can be invalid and break things #1110

rchiodo opened this issue Nov 13, 2020 · 5 comments · Fixed by #11109
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug notebook-getting-started verified Verification succeeded
Milestone

Comments

@rchiodo
Copy link
Contributor

rchiodo commented Nov 13, 2020

See the discussion here:
#513

Sometimes the jupyter interpreter can go out of date. We should verify it's still valid somehow before using it.

@rchiodo rchiodo added the bug Issue identified by VS Code Team member as probable bug label Nov 13, 2020
@Mjboothaus
Copy link

Yes - I think I'm coming across this sort of issue within my Gitpod.io environment.

Basically I'm defining an environment completely via code (in this case .gitpod.yml - which in turn contains shell commands to install a conda environment which is then added as a Juypter kernel).

So I end up with a conda environment called say MY_ENV_NAME and I am installing this as a Jupyter kernel i.e.

python -m ipykernel install --user --name=MY_ENV_NAME

as part of the build script. So the kernel is installed to:

/home/gitpod/.local/share/jupyter/kernels/MY_ENV_NAME

However notebooks that I have been successfully using and running with this conda environment, when I re-launch the Gitpod environment it is opening the notebook, but it is failing to recognise the environment.

Interestingly, this was working beforehand but has just broken somewhere in the infrastructure i.e. either Gitpod or VS Code which makes it difficult to track down.

@rzhao271
Copy link
Contributor

What are some verification steps for this issue?

@Mjboothaus
Copy link

As you can appreciate this issue was sometime ago now and while I can recall the behaviour I don't have a specific example at hand.

I suspect both VS code and get pod have changed significantly since then – and I have not been using it pod very much since then because of the issue at the time.

When I get a moment I might re-try using my gitpod environment from before
Cheers

@Mjboothaus
Copy link

https://github.com/DataBooth/db-hello-gitpod

I think the .Gitpod.yaml file in this repo was the example I was running at the time

@DonJayamanne DonJayamanne added verified Verification succeeded and removed verification-steps-needed Steps to verify are needed for verification labels Jan 29, 2023
@DonJayamanne
Copy link
Contributor

No one has reported this for a while, hence marking as verifeid

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 9, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug notebook-getting-started verified Verification succeeded
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants