Problems with Notebook debugger (using Jupyter Protocol)

[DonJayamanne]

Note: These issues have been fixed for IW debugger, we need to fix them for Notebook

• Problem 1:

  • Cell 1

    < empty line>
    < empty line>	  
    < empty line>
    < empty line>
    print(1)
    print(2)

  When debugging the above code, the debugger will stop at line print(1), however when you hit step over in RBL or continue in the cell debugger it will break there once again.

• Problem 2:

  • Cell 1

    < empty line>
    < empty line>	  
    < empty line>
    def foo():
        print('inside foo')

    • Cell 2

    foo()

    When debugging the above code, the debugger will stop at line foo(), however when you step into the code, it will stop way above the def foo, in a white space (basically on line 2 of the file, in the white space).

• Problem 3:
  The above issues were uncovered while running some of the IW debugger tests.
  I think we need a few more tests for the notebook debugger to cover the same scenarios covered in IW debugger.

These issues have been fixed in the new IW when using debugger protocol.
Basically injecting breakpiont() along with a few other changes.

[roblourens]

I can't repro issue 1 in a notebook. I see issue 2 though, didn't know that Jupyter does this

[DonJayamanne]

@roblourens the empty lines were stripped by Github when rendering the sample code I added above... lol, Jupyter does the same,
Try with the leading empty lines (as per udpated sample code - which clearly shows where we need empty lines).

[DonJayamanne]

@ttSpace
please could you file a separate issue for that.

[DonJayamanne]

Upstream issue microsoft/debugpy#964 & microsoft/debugpy#869

[DonJayamanne]

Issues with empty lines will not be resolved for now (as it was reported by me and a papercut),
Creating a new issue to track breakpoint issue caused by upstream python debgger #10600

[roblourens]

Was problem 2 supposed to be fixed by the debugpy update?