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

Debugger breaks in interactiveshell.py #374

Closed
maximilianmordig opened this issue Jul 5, 2024 · 3 comments
Closed

Debugger breaks in interactiveshell.py #374

maximilianmordig opened this issue Jul 5, 2024 · 3 comments
Assignees
Labels
triage-needed Needs assignment to the proper sub-team

Comments

@maximilianmordig
Copy link

maximilianmordig commented Jul 5, 2024

Type: Bug

Behaviour

Whenever I debug a cell in an interactive window, it first stops at the interactiveshell.py even though I have not set a breakpoint there, so I have to hit F5 to get to the actual breakpoint.
I generally use justMyCode=False because I also want to step into libraries, but only where I set breakpoints.
This is related to microsoft/vscode-jupyter#9815, which is closed for comments.

Steps to reproduce:

Debug a cell with justMyCode=False.

image

image

Diagnostic data

Output for Python in the Output panel (ViewOutput, change the drop-down the upper-right of the Output panel to Python)

XXX

Behaviour

XXX

Steps to reproduce:

  1. XXX

Diagnostic data

launch.json configuration

XXX

Output for Python in the Output panel (ViewOutput, change the drop-down the upper-right of the Output panel to Python)

XXX

Output for Python Debugger in the Output panel (ViewOutput, change the drop-down the upper-right of the Output panel to Python Debugger)

XXX

Extension version: 2024.6.0
VS Code version: Code 1.90.2 (Universal) (5437499feb04f7a586f677b155b039bc2b3669eb, 2024-06-18T22:37:41.291Z)
OS version: Darwin arm64 22.6.0
Modes:
Remote OS version: Linux x64 6.2.0-36-generic
Connection to 'SSH: mikado' could not be established Canceled
Connection to 'ssh-remote+mikado' could not be established
Connection to 'SSH: mikado' could not be established Canceled
Remote OS version: Linux x64 6.2.0-36-generic

  • Python version (& distribution if applicable, e.g. Anaconda): 3.10.12
  • Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): VirtualEnvironment
System Info
Item Value
CPUs Apple M2 Pro (12 x 2400)
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
webgl: enabled
webgl2: enabled
webgpu: enabled
Load (avg) 2, 2, 2
Memory (System) 16.00GB (0.21GB free)
Process Argv --crash-reporter-id 3133677a-c9e5-4743-9d41-dd5ce026400a
Screen Reader no
VM 0%
Item Value
Remote SSH: mikado
OS Linux x64 6.2.0-36-generic
CPUs Intel(R) Xeon(R) CPU E5-2690 v3 @ 2.60GHz (48 x 1200)
Memory (System) 125.80GB (114.32GB free)
VM 0%

Connection to 'SSH: mikado' could not be established Canceled

Connection to 'ssh-remote+mikado' could not be established

Connection to 'SSH: mikado' could not be established Canceled

Item Value
Remote SSH: mikado
OS Linux x64 6.2.0-36-generic
CPUs Intel(R) Xeon(R) CPU E5-2690 v3 @ 2.60GHz (48 x 1200)
Memory (System) 125.80GB (114.32GB free)
VM 0%
A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscorecescf:30445987
vscod805cf:30301675
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
962ge761:30959799
pythongtdpath:30769146
welcomedialogc:30910334
pythonnoceb:30805159
asynctok:30898717
pythonregdiag2:30936856
pythonmypyd1:30879173
2e7ec940:31000449
pythontbext0:30879054
accentitlementst:30995554
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
jchc7451:31067544
chatpanelc:31048052
dsvsc021:30996838
da93g388:31013173
pythoncenvpt:31062603
a69g1124:31058053
dvdeprecation:31068756
dwnewjupyter:31046869
2f103344:31071589
legacy_priority:31082724

@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label Jul 5, 2024
@paulacamargo25
Copy link
Contributor

Thanks for your bug report, any idea what is happening here @rchiodo?

@rchiodo
Copy link
Contributor

rchiodo commented Jul 18, 2024

This is by design or really a side effect of just my code being off. The kernel is stepping through code and with just my code off this entry is hit. There's really no workaround without adding some sort of custom callstack filtering to debugpy for this exact situation. It would be like stepThroughAllCodeExceptTheKernel or something like that.

@paulacamargo25
Copy link
Contributor

Thanks @rchiodo, i am closing the issue since this is not handle in the Python debugger extension. Feel free to create a feature-request in https://github.com/microsoft/debugpy.

@paulacamargo25 paulacamargo25 closed this as not planned Won't fix, can't repro, duplicate, stale Jul 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage-needed Needs assignment to the proper sub-team
Projects
None yet
Development

No branches or pull requests

4 participants