-
-
Notifications
You must be signed in to change notification settings - Fork 43
Extra breakpoints created every character typed #414
Comments
Thanks for the issue and demo. Yes, the content of the cell needs to be dumped as a file on the backend to be able to set breakpoints (more info in #49, #162, #64) Since the cells are identified using the murmur hash of their content, this is why they show up as different files with breakpoints. One thing that could be done is to only show the breakpoints for the visible cells in the notebook, even though more exist as files on the backend. Some of this is discussed in https://github.com/jupyterlab/debugger/issues/171. |
I think keeping the breakpoints for the whole notebook is pretty convenient. Another solution could be to "remember" when a cell gets the focus, and if its content is changed, first send a setBreakpoint request with an empty breakpoints list to the backend. This way the backend keeps the list of actual breakpoints, not the whole history. |
@JohanMabille Thanks for explanation What we need is to get the path when the cell gets the focus, and remember it.
From "hold-on" state:
|
This should now be fixed (by #436 and #474) Can be tested on Binder: https://mybinder.org/v2/gh/jupyterlab/debugger/master?urlpath=/lab/tree/examples/index.ipynb |
When I edit a line with a breakpoint, it seems to create new breakpoints for the edits as I type them in, rather than just when I run the cell. This is in JLab 2.1.0rc0 and:
Here, when I type "myvar", I am just pausing, and after every character I type a new breakpoint appears.
The text was updated successfully, but these errors were encountered: