Vscode-jupyter: Python interactive window not working!

[PrateekArya]

Issue Type: Bug

Python interactive stopped working just after updating to the current insider build.
Disabled all other extensions except for python, updated python extension, reset all python extension settings to default, restarted my computer, etc. Nothing seems to be working. Its stuck at "Executing Cell" status and the "Python Interactive" window frame is completely blank.

Steps to reproduce:

1. Open any .py file with "#%%" for marking cells.
2. Execute any cell.

VS Code version: Code - Insiders 1.47.0-insider (0913b1aa43191d8af0ccb4a133d9a8d7c1a81d69, 2020-06-23T09:03:35.861Z)
OS version: Windows_NT x64 10.0.18363

System Info

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz (12 x 3696)|
|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
viz_display_compositor: enabled_on
webgl: enabled
webgl2: enabled|
|Load (avg)|undefined|
|Memory (System)|63.84GB (55.76GB free)|
|Process Argv|D:OneDrive - NTNU0.3. Codes & Workspaces4. SSW DTUSLy-CalmW|
|Screen Reader|no|
|VM|0%|

Extensions (1)

Extension|Author (truncated)|Version
---|---|---
python|ms-|2020.7.89046-dev

[IanMatthewHuff]

@PrateekArya Does this just happen on occasion? Or every time? There is currently a known issue with VSCode in general where starting up webviews will occasionally fail and show a blank webview.

If you run the command "Developer: Open Webview Developer Tools" from the VSCode command palette do you see any errors in the "Console" tab? That might help to diagnose this.

[PrateekArya]

@IanMatthewHuff This happens every time for this insider build. It doesn't work at all.

Here is the Console tab error:

[PrateekArya]

@IanMatthewHuff It seems like it was a problem with vscode and they are saying that it is fixed now. I'll see if it is resolved in the next insider build (hoping that it will be released soon). :)

https://github.com/microsoft/vscode/issues/100865#event-3475266250

[greazer]

We believe this has been resolved.

[morhadar]

Im facing the same issue in the latest insider updated:

Version: 1.51.0-insider (user setup)
Commit: bb16786cff3d231facbdcee90741ac25fcffd3ac
Date: 2020-10-28T05:57:23.779Z
Electron: 9.3.3
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Windows_NT x64 10.0.17763

[IanMatthewHuff]

@morhadar this is actually a new issue introduced in insiders only, it's being tracked by microsoft/vscode-jupyter#500 and a fix is in progress already. You can move to stable as a workaround for now.