dotnet/interactive

Polyglot Notebook: [NetTestingE2E] Unable to run and stop execution the cell.

Closed this issue · 2 comments

Describe the bug
Using extension Polyglot Notebook in VS Code
The cell is unable to run and the function of "Stop Execution" doesn't work.

Detailed Repro Build info: VSCodeUserSetup-x64-1.100.3 +dotnet-interactive-vscode-1.0.6304011.vsix
Version: 1.100.3 (user setup)
Commit: 258e40fedc6cb8edf399a463ce3a9d32e7e1f6f3
Date: 2025-06-02T13:30:54.273Z
Electron: 34.5.1
ElectronBuildId: 11369351
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.19045

dotnet-interactive-vscode-1.0.6304011.vsix
build link: https://dev.azure.com/dnceng/internal/_build/results?buildId=2722809&view=artifacts&pathAsName=false&type=publishedArtifacts

sdk info: dotnet-sdk-9.0.300-win-x64.exe

Note:
1.It's a regression issue. It is not repro on VSCode 1.100.1 + dotnet-interactive-vscode-1.0.6262011.vsix.
2.Repro VM: 172.16.195.152

Steps:

  1. Ctrl +Shift + P => "Polyglot Notebook: Create new blank notebook"
  2. Select "Create as .dib"
  3. Select the cell contents to 1+1 and execute
  4. Click "Sop Execution"

Expected Results:
[2] should be shown in brackets and "Stop Execution" can work all the time, with no error.

Actual Results:
The cell is unable to run and the function of "Stop Execution" doesn't work.

Image

Please complete the following:
Which version of .NET Interactive are you using? (In a notebook, run the #!about magic command. ):

  • OS
    • Windows 11
    • [√ ] Windows 10
    • macOS
    • Linux (Please specify distro)
    • iOS
    • Android
  • Browser
    • Chrome
    • Edge
    • Firefox
    • Safari
  • Frontend
    • Jupyter Notebook
    • Jupyter Lab
    • nteract
    • [√] Visual Studio Code
    • Visual Studio Code Insiders
    • Visual Studio
    • Other (please specify)

I'm not able to repro this issue, maybe because running code that executes so quickly is resulting in a race.

Canceling slower-executing code is working fine for me.

Image

@jonsequitur Thanks a lot for your comment, and I verified this issue with VSCode-1.100.3 +dotnet-interactive-vscode-1.0.6310011.vsix, it works well. Hence closing it.

Image