No longer able to select kernel for Jupyter notebook

[Mjboothaus]

Bug description

I have a environment defined in .gitpod.yml file that creates a conda Python environment (including Jupyter notebooks). It has been working fine for a while now.

Steps to reproduce

When I fired up Gitpod today (from https://github.com/DataBooth/db-hello-gitpod) I can no longer select a Jupyter kernel.

This is the workspace instance - https://green-bass-o31gml56.ws-us15.gitpod.io

I tried stopping and starting the workspace and the behaviour is reproducible.

Expected behavior

When you click Select Kernel within the notebook interface within VS Code you normally can choose from a list of (Python) environments -- but there are now no choices.

Example repository

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

Anything else?

Really loving Gitpod.

[Mjboothaus]

So trying to work out what has changed and broken this (as there were no changes in the .gitpod.yml file).

Here are the Editor: Help -> About details:

Version: 1.59.0
Commit: 330c9b35c2f3d95af9192bc1ce23eccc5fcbe808
Date: 2021-08-30T07:53:57.621Z
Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/14.1.2 Safari/605.1.15

[Mjboothaus]

So I assume it is something in the Gitpod (custom) VS Code editor build that has broken this functionality. I will try opening the notebooks via jupyter notebook in the command line as a work-a-round.

[Mjboothaus]

So work-a-round not working at least initially as the notebook via browser is not able to find the kernel.

This might be a Jupyter config issue in this setup - although it is puzzling.

[Mjboothaus]

So this is certainly a blocker -- I'm wondering where I can see release details for Gitpod releases, VS Code releases etc. in a centralised way so that it is easier to pinpoint what part of the chain has been broken.

[Mjboothaus]

Hmmm... still trying to work-a-round:

From Command Palette I tried to Select Interpreter to Start Jupyter server

without success. I also tried to re-install the kernel via:

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

which resulted in:

Installed kernelspec ENV_NAME in /home/gitpod/.local/share/jupyter/kernels/ENV_NAME where ENV_NAME is the label I use for my conda environment. But this doesn't seem to have resolved it.

[Mjboothaus]

Maybe this is related to these types of issues:

microsoft/vscode-jupyter#513

microsoft/vscode-jupyter#2282

[csweichel]

/schedule

[roboquat]

@csweichel: We have more than 16 cards scheduled. Above 0 only scheduler can perform this action. Those are:

In response to this:

/schedule

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[csweichel]

/schedule

[roboquat]

@csweichel: We have more than 16 cards scheduled. Above 0 only scheduler can perform this action. Those are:

In response to this:

/schedule

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[akosyakov]

Maybe related to these changes: gitpod-io/workspace-images#461 cc @aledbf @AlexTugarev could it be related?

[jeanp413]

@Mjboothaus do you have a public repo that I can use and try to reproduce? I can't access https://github.com/DataBooth/db-hello-gitpod

[Mjboothaus]

Hello Jean Pierre Yes - I meant to publish it as a public repo. Will try to do that shortly. Cheers, Michael

…

On 2 Sep 2021, at 2:08 am, Jean Pierre ***@***.***> wrote: @Mjboothaus <https://github.com/Mjboothaus> do you have a public repo that I can try to reproduce? I can't access https://github.com/DataBooth/db-hello-gitpod <https://github.com/DataBooth/db-hello-gitpod> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#5467 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHJQEOETXOQ7KG6IAGO4QLT7ZFYVANCNFSM5DE3D72A>.

[Mjboothaus]

https://github.com/DataBooth/public-hello-gitpod Is a public version of the repo I have just tested it in Gitpod i.e. opened the notebook in the notebook directory and I still can’t Select Kernel. Cheers :)

…

On 2 Sep 2021, at 6:14 am, Michael Booth ***@***.***> wrote: Hello Jean Pierre Yes - I meant to publish it as a public repo. Will try to do that shortly. Cheers, Michael > On 2 Sep 2021, at 2:08 am, Jean Pierre ***@***.*** ***@***.***>> wrote: > > > @Mjboothaus <https://github.com/Mjboothaus> do you have a public repo that I can try to reproduce? I can't access https://github.com/DataBooth/db-hello-gitpod <https://github.com/DataBooth/db-hello-gitpod> > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub <#5467 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHJQEOETXOQ7KG6IAGO4QLT7ZFYVANCNFSM5DE3D72A>. >

[akosyakov]

@Mjboothaus which version of python extension do you run? Latest from Open VSX? nvm I think i figured it out

[Mjboothaus]

Hi Anton — thanks for your question. As per the conda environment.yml file in the repo: dependencies: - python >=3.8,<3.9 Currently conda is installing: conda 4.10.3 Python 3.8.10 in the (conda) environment. Cheers, Michael

…

On 2 Sep 2021, at 5:05 pm, Anton Kosyakov ***@***.***> wrote: @Mjboothaus <https://github.com/Mjboothaus> which version of python extension do you run? Latest from Open VSX? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#5467 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHJQEIAJVPYU6Z7JXIMIGTT74O35ANCNFSM5DE3D72A>.

[akosyakov]

Python extension in Open VSX is old and not compatible with VS Code 1.59 anymore. I can upgrade it but it does not seem to fix the problem. I'm looking into whether Select Kernel requires another extension right now or it is misconfiguration in our workspace image.

[Mjboothaus]

[Mjboothaus]

Thanks @akosyakov -- just looked up the MS Jupyter extension history and it seems some work is happening there currently.

[Mjboothaus]

I feel the 2.5 star rating for the extension is a little harsh :)

Oh - so Open VSX is an alternate market place for VS Code extensions...

All I can say is my .gitpod.yml setup was working perfectly for the past month or so and then stopped abruptly on Wed AM Sydney (AEST GMT+10).

Great work the Gitpod.io team is doing!

[akosyakov]

Oh - so Open VSX is an alternate market place for VS Code extensions...

Yes, I mean there it is out-dated

All I can say is my .gitpod.yml setup was working perfectly for the past month or so and then stopped abruptly on Wed AM Sydney (AEST GMT+10).

VS Code 1.59 was released, but we don't have smoke tests for notebooks yet 🙈

[Mjboothaus]

Seems I'm smoking... (whether I like it or not) 🚬

[akosyakov]

So we should pbulish python and jupyter notebook extensions which are compatible with 1.59 to Open VSX and list jupyter notebook as allow proposed apis in product.json. I will send PRs. But in the best case I can promise only next Wednesday.

[akosyakov]

Yes, it helps in testing environments:

Working on fixing publishing to Open VSX.

[Mjboothaus]

👍🏻