vscode-jupyter: Error loading preloads: Could not find renderer
All of a sudden the jupyter extension has problems with ipywidgets. Yesterday I started getting this error whenever I use tqdm and display(dataframe) in a notebook.
Error loading preloads:
Could not find renderer
Yesterday I had to reinstall the VSC python tools (including vscode-jupyter) and the conda environment I use inside of a remote environment: that is the only change with respect to two days ago, when there were no issues at all. The conda environment was built using a yaml file (conda env export > env.yaml) that was used to create the environment in use two days ago.
Both the local and the remote machines run linux.
The VSC extension Jupyter Notebook Renderers is installed, version v1.0.6.
I tried to uninstall and reinstall the Jupyter extension (as suggested somewhere), but with no effects.
Environment data
Version: 1.66.2 Commit: dfd34e8260c270da74b5c2d86d61aee4b6d56977 Date: 2022-04-11T07:49:24.808Z Electron: 17.2.0 Chromium: 98.0.4758.109 Node.js: 16.13.0 V8: 9.8.177.11-electron.0 OS: Linux x64 5.13.0-40-generic
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 3
- Comments: 16 (6 by maintainers)
I sunk something like 3 hours Uninstalling the Jupyter extension, reloading VS Code, reinstalling the extension, re running the notebook, getting the same error, uninstalling the Jupyter notebook Renderers extension, reloading VS code, reinstalling both Jupyter and the Notebook Renderers extension, rerunning the notebook, etc.
The “Select Kernel” button stops working, and says “Install kernels from the marketplace” even though I had just run the notebook with a kernel. So then you have to uninstall Jupyter extension yet again and reload, reinstall it…
What a mess.
Eventually through some random permutation of older versions of the extension it worked. I think it was basically some earlier version of the VScode-Jupyter extension (~ over 2 months before the current release) that ultimately made the
Error loading preloads: Could not find renderererror go away.But I’ve sunk far too much time trying to fix this bug and can no longer afford any more.
The VS Code Jupyter extension has caused incalculable amount of stress, frustration, and lost time for myself and other users.
TLDR, the Jupyter extension needs some serious work in stability and reliability.
On Thu, Jun 16, 2022, 2:16 PM Rich Chiodo @.***> wrote:
Hello and thanks for your anwer. I was finally able to have it working again, but I needed to uninstall / reinstall / close CSV / reopen VSC.
I think my installation has become a little messy after this round of updates since I have problems with many other extensions. Not even python code autocompletion works anymore. I think it would be better if a VSC version could install only versions of an extension that are compatible with it (in this case 1.66).
Update: after updating to 1.67 many of the problems seem solved. It seems updates are compulsory with VSC.
The pre-release version can solve this issue. After I switched to pre-release version, it’s ok.
This issue still exists… QThans suggested switching to pre-release version which works for me as well…
Exaxtly. The only way to solve the issue was (now I am not experiencing it any more) to try plenty of permutations of install/unistall/enable/…
Il gio 16 giu 2022, 21:25 Cpop @.***> ha scritto: