IPyKernel not installed into interpreter is logged as unhandled errors against extension

had a small problem, manually installed by hitting the install button…

Edition Windows 10 Pro Version 21H1 Installed on ‎3/‎12/‎2021 OS build 19043.1348 Experience Windows Feature Experience Pack 120.2212.3920.0

far as i know it will be fine till i find another problem, sorry to be a bother 😕 (im new and getting situated…) if you need any other information than my vague input…well…you know

Environment data

• VS Code version: Python 1.62.3
• Jupyter Extension version (available under the Extensions sidebar): XXX
• Python Extension version (available under the Extensions sidebar): XXX
• OS (Windows | Mac | Linux distro) and version: XXX
• Python and/or Anaconda version: python 3.10.0
• Type of virtual environment used (N/A | venv | virtualenv | conda | …): XXX
• Jupyter server running: Local | Remote | N/A

Expected behaviour

XXX

Actual behaviour

XXX

Steps to reproduce:

[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]

1. XXX

Logs

Output for Jupyter in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Jupyter)

XXX

[rchiodo]

Actually I’m not sure there’s even an error? It looks like the install worked. Were you able to run a cell?

[DonJayamanne]

@rchiodo I’m gong to re-open this, so we don’t log the messages as errors. Basically these are handled, hence logging them into console as errors only adds to the confusion. Changing this to debt

TODO:

• Stop logging ipykernel not found as errors, instead log them as warnings or info.

Why: These errors are logged & displayed as unhandled errors, which isn’t true. hence confuses users.