Debug Cell option disappears

wcneill commented 2 years ago

Environment data

VS Code version: XXX
Jupyter Extension version (available under the Extensions sidebar): v2022.4.1021342353
Python Extension version (available under the Extensions sidebar): v2022.6.2
OS (Windows | Mac | Linux distro) and version: Windows
Python and/or Anaconda version: Python 3.8.8
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda
Jupyter server running: Local | Remote | N/A: Local and Remote

Expected behavior

A small drop down arrow next to the run cell, which shows a debug cell option:

Actual behavior

The drop down arrow disappears after a single debug run, and using the ctrl + shift + alt + enter to key combo to debug the cell is also unresponsive. Sometimes it comes back in a few minutes of waiting and sometimes I have to restart VS Code.

Steps to reproduce:

Start a notebook
Debug a cell
The down arrow disappears.

Logs

Output for Jupyter in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Jupyter)

``` XXX ```

pascal-g-shift commented 6 months ago

1.87.2 on Windows still there

weavermech commented 5 months ago

Just happened on 1.88.1 Windows 10

aringer117 commented 5 months ago

Same issue on 1.89.0 and Windows 10. Restarting VC resolves till it "disappears" again.

Tremirre commented 5 months ago

Same for 1.89.0 on Win 11 In my case restarting VC does not resolve the issue - the debug option is not visible on kernel start (but after switching between tabs the option reappears)

epicwhale commented 5 months ago

+1 to this issue, really annoying!

Version: 1.90.0-insider
Commit: 0cd8d6ac480bc5b4e2a2d7f1eb87eaff9f7d47e1
Date: 2024-05-16T05:50:49.491Z

MiguelTerraNeves commented 5 months ago

+1, the negative productivity impact of this is huge, not even closing and reopening the notebook is fixing this for me now

petermchale commented 4 months ago

Same issue here.

Version: 1.89.1 (Universal) Commit: dc96b837cf6bb4af9cd736aa3af08cf8279f7685 Date: 2024-05-07T05:14:24.611Z Electron: 28.2.8 ElectronBuildId: 27744544 Chromium: 120.0.6099.291 Node.js: 18.18.2 V8: 12.0.267.19-electron.0 OS: Darwin arm64 23.5.0

mvccn commented 3 months ago

this has been two years, still no fix? this is an very annoying bug. why is the team ignoring this.

JonathanMushkin commented 3 months ago

Same problem here, MacOS Senoma 14.5. VScode verision: Version: 1.91.1 (Universal) Commit: f1e16e1e6214d7c44d078b1f0607b2388f29d729 Date: 2024-07-09T22:07:54.982Z (1 wk ago) Electron: 29.4.0 ElectronBuildId: 9728852 Chromium: 122.0.6261.156 Node.js: 20.9.0 V8: 12.2.281.27-electron.0 OS: Darwin arm64 23.5.0

lainiewoodyard22 commented 3 months ago

What still no fix

SaturnTsen commented 2 months ago

still no fix...

thesyntaxinator commented 2 months ago

bump

andrearosasco commented 2 months ago

bump

starball5 commented 2 months ago

If people keep adding bump comments, expect this issue ticket to get locked to maintainers only. I don't think we want that.

JohnAtl commented 2 months ago

I'm not sure this is still an issue for me. The only time the debug option isn't available is when a kernel hasn't been selected.

oresthes commented 3 weeks ago

Exact same problem here:

Version: 1.93.1 Commit: 38c31bc77e0dd6ae88a4e9cc93428cc27a56ba40 Date: 2024-09-11T17:20:05.685Z Electron: 30.4.0 ElectronBuildId: 10073054 Chromium: 124.0.6367.243 Node.js: 20.15.1 V8: 12.4.254.20-electron.0 OS: Linux x64 5.15.0-122-generic

This is really really annoying

microsoft / vscode