Interrupt kernel doesn't report status when failed to interrupt and kernel crashed

[ronglums]

1. Run all cells on this code:
   #%% [markdown]

## This is markdown.

#%%

Let's load and review some data

import pandas as pd # pandas is a dataframe library
df = pd.read_csv("./data/pima-data.csv") # load Pima data
df.head(5)

#%% Let's plot the correlation between data columns
import matplotlib.pyplot as plt # matplotlib.pyplot plots data
import matplotlib.style as style
style.use('dark_background')

def draw_corr(df, size = 11):
corr = df.corr() # data frame correlation function
fig, ax = plt.subplots(figsize=(11, 11))
ax.matshow(corr) # color code the rectangles by correlation value
plt.xticks(range(len(corr.columns)), corr.columns) # draw x tick marks
plt.yticks(range(len(corr.columns)), corr.columns) # draw y tick marks

draw_corr(df)

2. Then immediately hit the "Interrupt kernel" button.
3. Executing get stuck on the 3rd cell with status bar showing "Executing Cell" but it never finishes.

What happened was that the kernel wasn't interrupt-able at the time and it crashed and restarted itself, but VS Code doesn't report that status. And if trying to run more cells at this point, the execution order shows [-2].

[ronglums]

A Jupyter-like message would be helpful.

[rchiodo]

The SessionManager.runningChanged signal might fire when this problem occurs.

[ronglums]

1. If Jupyter is not interruptable (check timeout limit), prompt if a restart is desired.
2. If Jupyter crashed and restarted, show a message.

[rchiodo]

Hmm. Having a problem fixing this. Jupyter is not interrupting anything:
ipython/ipython#3400

[rchiodo]

Should be fixed now in our insiders build