Skip to content

Select Kernel ineffectual #16654

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
MadameMinty opened this issue May 19, 2025 · 3 comments
Open

Select Kernel ineffectual #16654

MadameMinty opened this issue May 19, 2025 · 3 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug
Milestone

Comments

@MadameMinty
Copy link

Type: Bug

  1. Open latest VSCode Insiders.
  2. Open a .ipynb file.
  3. Click "Select Kernel" / invoke "Notebook: select notebook kernel" in any way.
  4. Pick any kernel from the list. The list will close.
  5. No kernel is selected. Cells won't run.

Extension version: 2025.4.0
VS Code version: Code - Insiders 1.101.0-insider (18ed64835ec8f8227dbd8562d2d9fd9fa339abbb, 2025-05-19T02:31:52.657Z)
OS version: Windows_NT x64 10.0.19045
Modes:

System Info
Item Value
CPUs AMD Ryzen 5 3600 6-Core Processor (12 x 3600)
GPU Status 2d_canvas: enabled
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
webnn: disabled_off
Load (avg) undefined
Memory (System) 31.95GB (12.61GB free)
Process Argv D:\git\__envs\Pathosense.code-workspace --crash-reporter-id 3a5b591f-520b-44f3-9886-67366bc5af70
Screen Reader no
VM 0%
@MadameMinty
Copy link
Author

Additional details:
VSCode (Release): both versions of the extension seem to work.
VSCode Insider: Seems to work when I switch the extension to Pre-Release version. Stops working when I switch back to Release. So it seems like a VSCode Insider + Jupyter Release combo issue. Might actually be core VSCode Insider fault.

@rebornix rebornix added bug Issue identified by VS Code Team member as probable bug important Issue identified as high-priority labels May 23, 2025
@rebornix rebornix added this to the May 2025 milestone May 23, 2025
@rebornix
Copy link
Member

I found that it's broken only when Python Environments ms-python.vscode-python-envs is installed. It threw an exception about missing executable.

@rebornix rebornix removed the important Issue identified as high-priority label May 23, 2025
@DonJayamanne
Copy link
Contributor

@MadameMinty pleaser can you install three latest version 2025.4.1
This should be fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

No branches or pull requests

4 participants