No kernel connected message after reloading interactive window

[joyceerhl]

Testing #186191

1. Create interactive window
2. Clear all cells
3. Reload window
4. Interactive window restores, kernel gets reselected, but I get a message saying 'No kernel connected'

[amunger]

after reloading, the kernel is selected, but not connected. I can try to come up with a better message for this

[joyceerhl]

Would it make sense to automatically start trying to reconnect to the kernel on a reload with a Connecting to kernel <kernel name>... message? This seems to be what we do for Jupyter notebooks

[amunger]

This seems to be what we do for Jupyter notebooks

after reloading a notebook that previously had a kernel, I still see a 'connecting' toast when I run the first cell, so I don't think we auto connect for notebooks either

[joyceerhl]

Oh, I was thinking of the reconnection and continued execution of cells when the window gets reloaded while a cell is executing, which is what @DonJayamanne demoed a few weeks ago

[DonJayamanne]

I guess we could reconnect additionally, but then users would also expect the kernel state to persist, and that’sa whole separate issue

hence to avoid confusion, I wouldn’t auto reconnect just yet,
Do we even need to display a message about the fact that a kernel is not connected?

why not try without that message and see what users think?

I personally think we need a kernel status indicator (in toolbar or states bar) for notebooks (ipynb and IW), that would make this message totally unnecessary
We have a similar need for notebooks as well

[amunger]

a kernel status indicator is a great idea. I think there still needs to be some indication of a kernel restart since the IW is much more of a history view, but could definitely improve from what it currently looks like

[amunger]

closing in favor of microsoft/vscode-jupyter#14862