Kernel Interrupt not working in interactive window for cells submitted from a #%% file

[greazer]

Version: 1.59.0 (system setup)
Commit: 379476f0e13988d90fab105c5c19e7abc8b1dea8
Date: 2021-08-04T23:13:12.822Z
Electron: 13.1.7
Chrome: 91.0.4472.124
Node.js: 14.16.0
V8: 9.1.269.36-electron.0
OS: Windows_NT x64 10.0.22000

1. Run a long running notebook using a python script with #%% cells, run it via a codelens then try to stop it with Interrupt Kernel.

It doesn't stop. No notification that it's even trying to stop it as is expected.

[robclouth]

Same issue. After closing, the window opens again automatically because it's still running, then the Interrupt button works correctly.

[joyceerhl]

This is happening because cell execution for the interactive window is not managed through the KernelExecution codepath, so when we call interrupt here:

vscode-jupyter/src/client/datascience/interactive-window/nativeInteractiveWindow.ts

Line 505 in 27a2bf4

const result = await this.kernel.interrupt(notebookEditor.document);

There's no executionQueue, so we report success and never attempt the interrupt:

vscode-jupyter/src/client/datascience/jupyter/kernels/kernelExecution.ts

Lines 96 to 99 in f5c8929

	const executionQueue = this.documentExecutions.get(document);
	if (!executionQueue) {
	return InterruptResult.Success;
	}

The right fix here is probably to rework execution in the interactive window to use the KernelExecution codepath like native notebooks.

[joyceerhl]

Hotfixed in release branch for upcoming recovery build via #7070