Closed RaphaelNeubert closed 10 months ago
Hi!
I could (surprisingly) reproduce your issue, and seeing where it comes from, I guess you're the first user to try out Python3_jupyter for a looong time. (It was somewhat forsaken).
I have included the fix on the 'dev' branch (which you can try right now but then need to compile it, thus need Rust on your PC). You can also wait for the next v1.3.8 release, which will land in a couple days at most
For the sake on going in-depth:
Probably some debugging behavior from the last user who asked me to debug a very peculiar race condition... I now completely ignore my previous comment on the matter:
/// In theory, is a good idea, but somehow doesn't work
and reinstate the "wait that the jupyter kernel is ready" step that made everything work
Also, a loglevel meaning changed in jupyter-console (thanks jupyter devs) so my output was garbage for some time
merged and released in v1.3.8
Thank you very much, i will check it out once i get back home.
Sniprun works fine with Python3_original. When i use Python3_jupyter sniprun never returns anything after running it on trivial lines.
:checkhealth sniprun shows no issues jupyter-kernel and jupyter-console are installed.
The log located at ~/.cache/sniprun/sniprun.log shows a rust error:
I appreciate any help