-
Notifications
You must be signed in to change notification settings - Fork 293
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
Labels
Comments
Can confirm the same behavior on Windows. Environment data
|
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. |
I have the exact same issue on my ubuntru machine Environment data
|
After some testings, it seems that the issue is linked to ipykernel version 6.4.1 |
Duplicate of #8803 |
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
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
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
A/B Experiments
![vscode-debug-cell-issue](https://user-images.githubusercontent.com/28503057/152713735-6e439523-0586-4677-9ffc-227c838e64f9.gif)The text was updated successfully, but these errors were encountered: