Closed amunger closed 1 year ago
Thanks for filing this. I just wanted to make sure I understood what you saw since this is exactly the sort of thing I am looking into this month. Please grab the logs if you see it again.
It occured again out of the blue, ran a few cells, cancelled one, then tried to debug another with a breakpoint.
I can actually still use the kernel to keep running cells but RBL and debugging are disabled, and the debug toolbar is visible but doesn't seem to do anything
It looks like you don't have "jupyter.logging.level": "verbose"
, so the debug logs don't show up ðŸ˜
It looks like you did an interrupt right before the time that didn't work?
Oh, yes you said that
I already had log level at verbose for this repro - I can try to confirm if that's working correctly
You should see a lot of messages that look like [Debug] to kernel: {"command":"variables","arguments":{"variablesReference":6},"type":"request","seq":54}
my current state seems to be caused by https://github.com/microsoft/vscode-jupyter/issues/11528
I don't have a repro for this anymore, but I hit it across multiple kernel restarts and even a window reload.
I've tried several variations of these steps and can no longer repro, debugging a cell even works when I'm already debugging the extension.