Skip to content
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

Debug cell not working on macOS #8940

Closed
aljabadi opened this issue Feb 7, 2022 · 6 comments
Closed

Debug cell not working on macOS #8940

aljabadi opened this issue Feb 7, 2022 · 6 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s) notebook-debugging

Comments

@aljabadi
Copy link

aljabadi commented Feb 7, 2022

Issue Type: Bug

Debug cell launches the debugger but won't stop at breakpoint or show any signs of any execution. Trying to access the variables before the first breakpoint in debug console throws an error which probably means it is not just a UI issue. The debugger works just fine in interactive python files, but not in notebooks. This issue reproduces in the Insiders version. A gif will be attached.

Extension version: 2022.1.1001775990
VS Code version: Code 1.64.0 (5554b12acf27056905806867f251c859323ff7e9, 2022-02-03T04:20:22.135Z)
OS version: Darwin arm64 20.6.0
Restricted Mode: No

System Info
Item Value
CPUs Apple M1 (8 x 24)
GPU Status 2d_canvas: enabled
gpu_compositing: enabled
metal: disabled_off
multiple_raster_threads: enabled_on
oop_rasterization: enabled
opengl: enabled_on
rasterization: enabled
skia_renderer: disabled_off_ok
video_decode: enabled
webgl: enabled
webgl2: enabled
Load (avg) 2, 2, 2
Memory (System) 16.00GB (0.22GB free)
Process Argv --crash-reporter-id 9c18ce9b-c0c7-4fa0-a5c2-eecd7b2d0261
Screen Reader no
VM 0%
A/B Experiments ![vscode-debug-cell-issue](https://user-images.githubusercontent.com/28503057/152713735-6e439523-0586-4677-9ffc-227c838e64f9.gif)
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyl392:30425749
pythontb:30283811
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805cf:30301675
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
vsc1dst:30433059
pythonvs932:30410667
wslgetstarted:30433507
vscop940:30404999
vsrem710cf:30416617

@aljabadi
Copy link
Author

aljabadi commented Feb 7, 2022

vscode-debug-cell-issue

@jmigual
Copy link

jmigual commented Feb 7, 2022

Can confirm the same behavior on Windows.

Environment data

  • VS Code version: 1.64.0
  • Jupyter Extension version: v2022.1.1001775990
  • Python Extension version: v2022.0.1786462952
  • OS Windows and version: Windows 10 21H2 Build 19044.1503
  • Python and/or Anaconda version: Python 3.10.1
  • Type of virtual environment used (N/A | venv | virtualenv | conda | ...): poetry / virtualenv
  • Jupyter server running: Local

@jmigual
Copy link

jmigual commented Feb 7, 2022

As an addition, I found that if you add the breakpoint in the first line it works, while a breakpoint in any other line is ignored.

@Syndorik
Copy link

Syndorik commented Feb 7, 2022

I have the exact same issue on my ubuntru machine

Environment data

  • VS Code version: 1.65.0
  • Jupyter Extension version: v2022.1.1001775990
  • Python Extension version: v2022.0.1786462952
  • OS: Ubuntu 18.04
  • Python and/or Anaconda version: Python 3.9.10
  • Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda
  • Jupyter server running: remote

@Syndorik
Copy link

Syndorik commented Feb 7, 2022

After some testings, it seems that the issue is linked to ipykernel version 6.4.1
I have downgraded to ipykernel 6.4.0 and it works perfectly

@DonJayamanne
Copy link
Contributor

Duplicate of #8803

@DonJayamanne DonJayamanne marked this as a duplicate of #8803 Feb 7, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 8, 2023
@DonJayamanne DonJayamanne added the *duplicate Issue identified as a duplicate of another issue(s) label Nov 27, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s) notebook-debugging
Projects
None yet
Development

No branches or pull requests

4 participants