Interpreter picker seems to be displayed in Jupyter remote scenario

[DonJayamanne]

It should not show up.

[IanMatthewHuff]

Still repros.

[DonJayamanne]

Could be the active interpreter that we're displaying.

[DonJayamanne]

Could be caused by interactive window , as it doesn't support remote yet.

[DonJayamanne]

Should be fixed

[IanMatthewHuff]

This is still broken. I'm debugging now. Looks like there is a bigger issue here with extension activation.

[IanMatthewHuff]

This concerns me a bit. It looks like we are relying on onDidActivationPythonExtension, which from the code doesn't seem reliable. There are other places we are using this as well. I'm surprised that VS Code doesn't have a way to see when an extension is activated.

[IanMatthewHuff]

Dropping a quick note here, I see this as the probable issue here (per the comment):

vscode-jupyter/src/client/api/pythonApi.ts

Line 341 in 22f866c

this.apiProvider.onDidActivatePythonExtension(

In the remote case we are not getting this event to hook up. Which I believe could cause issues with the other usages of this.

[DonJayamanne]

FYI - I added this to october as its not a ship blocker

[rchiodo]

I think this is working? Not sure what the problem is.

This shows in the kernel picker for interactive window (when using remote)

IW starts fine with remote.

[rchiodo]

@DonJayamanne do you remember what the problem was here?