Cell debugging fails intermittently
See original GitHub issueDoes this issue occur when all extensions are disabled?: Yes/No
- VS Code Version: 1.68.0
- OS Version: macOS Montery 12.4
Steps to Reproduce:
- Create a new jupyter notebook
- Add some code and provide a breakpoint
- Run ‘Debug in cell’. The program does not honor the breakpoint at all
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:15 (7 by maintainers)
Top Results From Across the Web
How to debug intermittently failing connections to Azure IoT ...
I have a number of cellular devices deployed in Canada (with different mobile operators) and connecting to Azure IoT Hub West US 2...
Read more >debug cell in jupyter notebook never executes or ... - GitHub
Issue Type: Bug The debug cell feature has stopped working in jupyter notebooks, while still working in python scripts.
Read more >Debugging a intermittent bug by inducing failure and then ...
The fix I applied was a try-catch block to find and log exceptions, and then continue looping to pick up more jobs. The...
Read more >Excel Macro Troubleshooting Tips Debug and F8 Key Problems
Troubleshoot Excel macro if error message appears. Use Debug button to find and fix simple problem. Fix F8 key stops working.
Read more >7 Debugging Techniques to Speed Up Troubleshooting | Toptal
Tip #1: Remove or automate all the configuration needed for the application to run. How much configuration is required to get the software...
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 Free
Top 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
I created a separate issue since that one is more cut and dry, I’m not convinced that they are caused by the same issue - the new one just seems like we aren’t handling the reset message correctly.
Quite different than the original issue though - I just can’t do any more debugging a that point