With remote server specified, local kernels aren't listed if the server is down
See original GitHub issueType: Bug
This may be because I am in the remote experiment and also have
"jupyter.showOnlyOneTypeOfKernel": false
- Specify a jupyter server for remote kernels
- Kill the server
- reload vscode 🐛 only one of my local kernels is listed 🐛 cannot debug a cell 🐛 cannot create an interactive window
Extension version: 2022.9.1002791060 VS Code version: Code - Insiders 1.72.0-insider (a12109a6ac8cdb070d94d63a5dc3a3a8f53bad8c, 2022-10-04T12:24:00.023Z) OS version: Windows_NT x64 10.0.22621 Modes: Sandboxed: Yes
System Info
Item | Value |
---|---|
CPUs | Intel® Core™ i7-1065G7 CPU @ 1.30GHz (8 x 1498) |
GPU Status | 2d_canvas: enabled canvas_oop_rasterization: disabled_off 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_renderer: enabled_on video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: disabled_off |
Load (avg) | undefined |
Memory (System) | 31.59GB (12.12GB free) |
Process Argv | –crash-reporter-id 1202dc88-403d-4ebc-8393-af3551a8bd5b |
Screen Reader | no |
VM | 0% |
A/B Experiments
vsliv695:30137379
vsins829:30139715
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
vslsvsres303:30308271
pythonvspyl392:30422396
pythontb:30258533
pythonptprofiler:30281269
vshan820:30294714
pythondataviewer:30285072
vscod805cf:30301675
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30404738
cppdebug:30492333
vsclangdf:30492506
c4g48928:30535728
dsvsc012:30540252
pylantcb52:30568093
vsccc:30564266
pyindex848:30577858
Issue Analytics
- State:
- Created a year ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
jupyter server : not started, no kernel in vs code - Stack Overflow
I've selected "default", letting VSCode starting a server on the local (remote) host, and then the interpeter / kernel was enabled.
Read more >Setting Up KDNET Network Kernel Debugging Manually
Local link IP addresses are not routable, so a host and target cannot use a local link IP address to communicate through a...
Read more >DataSpell - Manage Jupyter notebook servers - JetBrains
Launch a local Jupyter server ... Once the server is launched, it is shown as a managed server in the list of the...
Read more >Chapter 10. Known issues Red Hat Enterprise Linux 8
Performing a RHEL installation with the reboot --kexec Kickstart command or the inst.kexec kernel boot parameters do not provide the same predictable system ......
Read more >What to do when things go wrong - The Jupyter Notebook
If your problem is with another kernel, not the Python one we maintain, ... your Notebook server, check out IPython's documentation for using...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Taking the “close” action as a verification. Otherwise please remove the tag.
the experiment was disabled with the setting, I just wanted to bring up that I was in the experiment in case that was causing issues. I was not seeing the “connect to local kernels” command, just a single one of my local kernels.
I just updated and attempted to capture a screenshot and this no longer repros for me: the cached remote kernel is still selected, and I am able to switch to a different kernel. I’ll just close this for now since I’m pretty sure I was the only one that saw this.