Address kernel startup and connection problems (okr)

[greazer]

• Interpreter is known to be conda, and no activation commands were found
• Interpreter is known to be conda, and activated environment variables were not generated
• Interpreter is known to be conda, and generating env variables failed
• Kernel not usable in VScode for Mac #6739
• "Running cells with {0} requires ipykernel" message has wrong interpreter displayName #6425
• WinPython interpreter is not loading. #6414
• Incorrect PYTHONPATH variable with .env file with relative paths #5061
• Use kernelspec.exe on windows when using kernelspec #1129
• .env file is ignored in a notebook and the interactive window #4593
• nbconvert can sometimes not be found, we should install it next to the extension like ipykernel #450
• Installing ipykernel fails with venv environment #1125
• Ship our own Jupyter to eliminate configuration problems #1131
• not able to start jupyter notebook imported into python using wsl when running as the root user #1124
• Jupyter Server: No Kernel Python: Not Started #1128
• Installing ipykernel requires admin on Windows #1253
• Installer for modules does not surface any errors when checking for if a module is installed #1257
• Add option to disable starting of multiple Kernels for a single interactive notebook #1269
• Lots of orphaned progress notifications after interactive window fails to open #1698
• Kernel won't start (heartbeat). May be related to use of --system-site-packages when defining virtual environment #1644
• With no workspace open, Jupyter server crashed. unable to connect. error code from jupyter: 1 #1591
• IPyKernel doesn't install correctly when powershell is default #421
• User belongs to experiment group & zmq crash #1440
• No SettingwithCopyWarning when expected (jupyter shows but VS code python doesn't) #617
• Trying to use old nonexistent kernel #1184
• Unresolved ipykernel installation - codespaces #4244
• WSL - jupyter notebook takes to long to open in VS Code Insiders. It's slow. loading performance  #5211
• Use VSC API to file an issue when there are kernel failures #5293
• Stuck on "starting kernel" when launching ansible-kernel #5394
• Kernel name initially not displayed and status is initially busy #5459
• Failed to change kernel [NoPermissions (FileSystemError): Unable to write file #5494
• Select kernel does not put up the 'install ipykernel' message #5736
• Impossible to run any notebook without Python extension when RAW isn't supported #5897
• Jupyter notebooks not using Python in current path #5998
• Active interpreter is being cached too long #6087
• microsoft/vscode-jupyter-internal#40
• microsoft/vscode-jupyter-internal#77
• microsoft/vscode-jupyter-internal#79
• microsoft/vscode-jupyter-internal#89
• microsoft/vscode-jupyter-internal#61
• microsoft/vscode-jupyter#5314
• FindMatchingInterpreter matching on interpreter path #5650

[rchiodo]

@jmew What's the telemetry being asked for here?

[DonJayamanne]

I added 2 I think will be required.

[jmew]

@rchiodo I think most of my telemetry asks were around Jupyter rather than conda (in a separate issue) so I cant think of any other ones off the top of my head right now for conda that arent in the original post.

[DonJayamanne]

Closing this issue, as this is old and outdated now.