Open ericpre opened 3 years ago
Hey @ericpre thanks for reaching out. When you say closing JupyterLab you mean closing the Webbrowser only? Or you mean shutting down the Jupyter server in the terminal?
Thanks for the quick reply and sorry for not being specific. With closing jupyterlab, I mean: "File" -> "Shut down" from the jupyter lab interface. If I kill the jupyter server from the terminal with "Control-C" it is different and the `mamba search --json" process is being stopped immediately.
If jupyterlab have been running for long enough (more than it takes for mamba search --json
to complete), in which case this process is not running, then jupyterlab closes as expected.
It seems that there are two different things going on:
mamba search --json
takes 1 or 2 min to complete, does it make sense?mamba search --json
Thanks for the reply.
I try not to get too much in technical details but trying to explain what is going on.
So first about mamba search --json
:
About why gator is not killing the task:
HTTP request between the frontend and the backend must be stateless and quick. So tasks in the extension are run in separated executors. The frontend needs then to ping the server to obtain the task status (and reply if it is finished). Unfortunately if the server shutdown is requested, I'm not aware of a notification system that will allow the extension to stop still running tasks - I asked on the server dev chat to know if this is possible.
Even if such notification exists, stopping running tasks needs to be done carefully because for example environment modification tasks should not be cancelled as it can corrupt the environment.
Thanks for the detailed explanation!
On mamba search --json
being slow: if I run mamba search
only, it only takes a couple of seconds (4-5s) while mamba search --json
is taking 1min30s on my setup. Is it something I shall report to mamba?
Even if such notification exists, stopping running tasks needs to be done carefully because for example environment modification tasks should not be cancelled as it can corrupt the environment.
Yes, indeed and we should expect users not to kill the server (or the process) when they started an update, which should be fine because an update would have triggered by the user.
I have noticed that gator starts the mamba search --json
every time that jupyterlab is started and this is not very convenient when opening a notebook just to check or copy some of its content, which I trend to do quite often. Maybe, the mamba search --json
process could be started only when gator is opened (through the menu "Settings/conda packages manager")?
mamba json
I'm not able to run that command using mamba 0.9.2 & conda 4.10.0.
Which version of mamba are you using?
I have noticed that gator starts the mamba search --json every time that jupyterlab is started
As the search take some times the idea is to trigger the listing refresh as quickly as possible. But your comment makes sense - it would be good to force this initial update only if the file is not there or if it is old (old being an user setting)
@ericpre contribution are welcomed if you want to give a try to implement this enhancement.
mamba json
I'm not able to run that command using mamba 0.9.2 & conda 4.10.0.
Which version of mamba are you using?
Sorry, it was a typo! I meant mamba search
without --json
- I edited the comment above.
@ericpre contribution are welcomed if you want to give a try to implement this enhancement.
I suspect that I don't know much about it, but I may have a look at it at some point - most likely not in the near future.
Sorry, it was a typo! I meant
mamba search
without--json
- I edited the comment above.
No problem - the json
option forces the command to output its results as json to be easily handled by code (like in this extension).
I suspect that I don't know much about it, but I may have a look at it at some point - most likely not in the near future.
No pressure 😉
Description
When gator is installed, mamba is still running after jupyter lab is closed: the GUI is closed but the mamba process is not completed and in the system monitor, I can see that
mamba search --json
is still running for about 1min 30s. Once this is done, the process is completed, i.e I can use the terminal prompt again. If mamba is not running when closing jupyterlab, then this issue doesn't occur.Reproduce
Expected behavior
The process should be stop immediately once jupyterlab stops.
Context
Command Line Output
Browser Output