Hello Praveen,
each user is running their own notebook server(s). You'll have to connect
to each of these servers in turn to query notebook status. But I don't
think your admin token will be accepted by those notebook servers.
You could change the authentication logic of the notebook servers
Hello Praveen,
I'd say one is the last activity of the user in general, the other is the
last activity of that particular server of the user.
The REST API looks as if a user can start multiple servers:
https://jupyterhub.readthedocs.io/en/stable/_static/rest-api/index.html
So the existing
Those are background threads of libzmq, as mentioned here:
https://github.com/zeromq/libzmq/blob/master/NEWS
Jupyter uses ZMQ to connect to the running kernels on the local machine.
There's not much to be done for the threads besides passing messages, so
they won't accumulate a lot of CPU time.
w way to go!
On Wed, Feb 20, 2019 at 6:00 PM Matthias Bussonnier <
bussonniermatth...@gmail.com> wrote:
> See the full announce on discourse:
>
> https://discourse.jupyter.org/t/release-of-ipython-7-3/409
>
> As usual available on PyPI, and on conda-forge.
> You can update with
> $ pip
See the full announce on discourse:
https://discourse.jupyter.org/t/release-of-ipython-7-3/409
As usual available on PyPI, and on conda-forge.
You can update with
$ pip install ipython --upgrade
And if you are using conda, once available on conda-forge:
$ conda upgrade ipython
The biggest
