Variable explorer: no variables defined

[ytyt-lead]

Issue Type: Bug

Variable explorer always shows "No variable defined", no matter how many cells did I run or how many variables did I create in every cell.
Yesterday variable explorer worked correctly, but today it shows only "No variable defined".
I tried to create new Jupyter Notebook, to restart VS Code, to reboot my PC - nothing changed.

Extension version: 2020.11.399280825
VS Code version: Code 1.51.1 (e5a624b788d92b8d34d1392e4c4d9789406efe8f, 2020-11-10T23:34:32.027Z)
OS version: Windows_NT x64 10.0.18363

System Info

Item	Value
CPUs	AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx (8 x 2296)
GPU Status	2d_canvas: enabled flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: disabled_off opengl: enabled_on protected_video_decode: unavailable_off rasterization: enabled skia_renderer: disabled_off_ok video_decode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled
Load (avg)	undefined
Memory (System)	9.94GB (4.83GB free)
Process Argv	--crash-reporter-id b0a3d91a-b073-470a-8715-c873fe3c9feb
Screen Reader	no
VM	0%

[ytyt-lead]

UPD: variable explorer breaks down after I create dictionary in any cell.
Steps to reproduce:

1. Open Variable explorer
2. Write "x = 'hello'" in a cell.
3. Run this cell: variable 'x' appears in Variable explorer.
4. Then create another cell and write "di = {'0': 1}. Run this cell.
5. Now Variable explorer freezes and even if you modify you 'x' variable, nothing changes.

[ytyt-lead]

[Screenshot] (http://joxi.ru/82Q94KOs9q87k2)
Cell #1-3 works fine.
Cell #4 causes crash.
And cell #5 doesn't update Variable explorer after running cell #4.

[IanMatthewHuff]

@Inspired1601 Currently looking into this. I don't repro this with the current bits from main that I have:

However when I pull our currently released public version of the extension I do see the issue here. Looks like this might be cleaned up in our upcoming release. Let me do one more quick check to verify.

[IanMatthewHuff]

@Inspired1601 Yes, this is fixed in our upcoming release bits. Sorry about the issue.