Can't debug a notebook after creating it.
See original GitHub issue- Create New File… -> Jupyter Notebook
- Add code. I used this, though it probably doesn’t matter.
def foo():
return 5
x = 5
- Set a bp on the x = 5 line.
- Start to debug the cell.
You’ll first be prompted to save the file, which I did.
But then after that you get this error: “Coudn’t find a debug adapter descriptor for debug type ‘Python Kernel Debug Adapter’ (extension might have failed to activate)”
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Debugging jupyter notebooks doesn't work after interrupting ...
Start run by line (click icon on cell toolbar, watch the screen recording) · Run to compltion · Debug again · At this...
Read more >Debugger in Jupyter Notebook does not work properly when I ...
Once I enter in a debug mode using Alt + Shift + Enter keys, it works and it stops at the break point...
Read more >Debuggers not acting properly on Jupyter notebooks
1 Answer 1 ; from IPython.core.debugger import ; def thisfunction ; x): x += 2 ; return x set_trace() # start debugging before...
Read more >VS Code tips — Debugging Jupyter notebooks - YouTube
Use ' Debug Cell' in VS Code to debug Python code cells in notebooks. Step through code, inspect variables, and even use the...
Read more >VSCode Jupyter Notebook Debugging Tutorial - YouTube
In this Visual Studio Code Tutorial Video, You'll learn ✓ A Quick Demo of VSCode Jupyter Notebook Debugging ✓ How to set up...
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 FreeTop 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
Top GitHub Comments
You beat me to it, forgot i had to add verified first…
I guess we still have it set to prompt a save before debugging, we only made that change for RBL. But seems like we should be able to support it. So not a regression