Unable to open 'file_name.ipynb': Cannot read property 'Rich' of undefined.

[SamuelManechez]

Issue Type: Bug

I want to open jupyter notebook on vscode insider but since the last update I have this issue : Unable to open 'file_name.ipynb': Cannot read property 'Rich' of undefined.

This file doesn't work on the standard vscode.

I hope you will patch this quickly.

Thanks !

Extension version: 2020.12.414227025
VS Code version: Code - Insiders 1.54.0-insider (6ac9a3ecb3698e82bf901f11bbb5940f6bc3c197, 2021-02-12T05:14:15.897Z)
OS version: Linux x64 5.4.0-65-generic

System Info

Item	Value
CPUs	Intel(R) Core(TM) i7-10850H CPU @ 2.70GHz (12 x 3500)
GPU Status	2d_canvas: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: disabled_off opengl: enabled_on protected_video_decode: unavailable_off rasterization: disabled_software skia_renderer: enabled_on video_decode: disabled_software vulkan: disabled_off webgl: enabled webgl2: enabled
Load (avg)	1, 0, 0
Memory (System)	30.97GB (28.41GB free)
Process Argv	--no-sandbox --unity-launch --crash-reporter-id 187279dd-b699-4c1d-94e3-4eb1f04f2c19
Screen Reader	no
VM	67%
DESKTOP_SESSION	cinnamon
XDG_CURRENT_DESKTOP	X-Cinnamon
XDG_SESSION_DESKTOP	cinnamon
XDG_SESSION_TYPE	x11

A/B Experiments

vsliv695:30137379
vsins829:30139715
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256198
vstry914:30244316
pythonvsdeb440:30224570
pythonvsded773:30223139
pythonvspyt600cf:30251589
core-portspanel:30233467
coreuntitledfile:30249963
openwsldoc:30257222

[deepan-py]

Same error

[ShuhuaGao]

Same error. Cannot open the existing .ipynb notebooks since the last update.

VS Code Insiders

• Version: 1.54.0-insider (user setup)
• Commit: 6ac9a3ecb3698e82bf901f11bbb5940f6bc3c197
• Date: 2021-02-12T05:13:16.111Z

Jupyter: v2020.12.414227025

[deepan-py]

Unable to open 'intro_.ipynb': Cannot read property 'Markdown' of undefined.

[claudiaregio]

Hi @SamuelManechez and @deepan-py , please see #4796 for more details

[jmsquare]

Same error