An example as in Jupyter notebook :

Is this more of a "nice to have" or does it solve a specific issue?
"nice to have"
does it solve a specific issue?
Possibly the issue of stopping the LiberTEM server if you didn't start it from a terminal, for example via https://github.com/sk1p/libertem-jupyter-proxy
does it solve a specific issue?
Possibly the issue of stopping the LiberTEM server if you didn't start it from a terminal, for example via https://github.com/sk1p/libertem-jupyter-proxy
Ok, good point!
Possibly the issue of stopping the LiberTEM server if you didn't start it from a terminal, for example via https://github.com/sk1p/libertem-jupyter-proxy
I would like to work on this, can you give some details regarding jupyter part.
You can try this yourself: run LiberTEM from jupyterlab, and kill the libertem-server process. What happens: does libertem-server stay dead, or is it revived? If it is revived, why is that? Example: the GUI keeps doing HTTP/websocket requests → this is easily fixable, other example: jupyter-proxy-server or how it's called just restarts any child processes → not so easy to fix, as it means we need to tell it to stop somehow
>
You can try this yourself: run LiberTEM from jupyterlab, and kill the libertem-server process.
actually how to kill libertem-server process alone :sweat_smile: . jupyter lab shows options to shutdown terminal and kernel session only.
kill libertem-server process alone
Using the process manager of the operating system, or, for example, kill on Linux.
Hey @AnandBaburajan can we collaborate on this issue?
Hey @AnandBaburajan can we collaborate on this issue?
Sure! I'll check the details and get back to you.
@twentyse7en So which part do you want me to focus on? Stopping the server or the button GUI part?
Edit: I don't think I can help you with this right now as my project schedule is a bit tight. I can definitely try after GSoC is over!
No problem, I will give a try.