Issue Type: Bug I'm sometimes (seems random) unable to select my python kernel. The Select Kernel options shows an empty list and I don't see any of my anaconda environments there. I also tried setting the interpreter by providing the co...
Open a folder with an ipynb file in it. Choose an existing kernel you know works. Open a Python Terminal via the command I would think that the Python terminal that's opened would match the environment selected for the notebook kernel. Instead you get the environment set for the Python ex...
I have the same issue for .ipynb files, with the additional bug that if I select kernel through the drop down list, nothing happens. It stays on the kernel in the conda environment I'm running the jupyter server from. If I select "Jupyter: Select kernel" from the command palette, after...
Create a new notebook file, "testnb.ipynb" - add and run a cell, make sure the my_venv Kernel actually starts. Exit code and fully delete my_env. Restart code and you can apparently never work with that notebook again - it indicates "No Kernel" in the top right but this cannot be...
Vscode reloads, I open a .ipynb file and vscode fails to connect at all. It's looking for some old kernel it can't find. I assume because there's some cache somewhere. Please note that when the logs mention localhost:9999 that port is bound via ssh tunnel to remoteserver:8888 where...
The new interpreter disappears from the jupyter kernel options every time after creating a new .ipynb file in vs code, restarting vs code or re-activating the virtual environments do not help. Occasionally, everything works normal, for instance, after I run a python file with the new python ...