If I open a server and exhibit activity on the server (e.g. open a notebook -> create and run cells and periodically save the notebook), it appears that my server gets removed, despite this activity.
Expected behaviour
I would anticipate that my server remains up-and-running.
Actual behaviour
The server gets removed.
How to reproduce
Start up a server
Edit a notebook, actively saving and running/adding cells
See after around --timeout + --cull-every seconds, the server gets culled.
Your personal set up
I am running JupyterHub in Docker with a SwarmSpawner subclass (VariableSwamSpawner) as a spawner class, with support for ContainDSDashboard.
OS:
Below is the Dockerfile I use for my jupyterhub server:
FROM jupyterhub/jupyterhub
COPY ./certs/ca-bundle.crt /usr/local/share/ca-certificates/
RUN pip install cdsdashboards oauthenticator dockerspawner ldap3 pyyaml jupyterhub-idle-culler && update-ca-certificates
COPY ./jupyterhub_config.py /srv/jupyterhub/jupyterhub_config.py
COPY ./templates /srv/jupyterhub/templates
# This command may be necesssary if jupyterhub complains about outdated database schemas
# CMD jupyterhub upgrade-db && jupyterhub
Bug description
If I open a server and exhibit activity on the server (e.g. open a notebook -> create and run cells and periodically save the notebook), it appears that my server gets removed, despite this activity.
Expected behaviour
I would anticipate that my server remains up-and-running.
Actual behaviour
The server gets removed.
How to reproduce
--timeout + --cull-every
seconds, the server gets culled.Your personal set up
I am running JupyterHub in Docker with a
SwarmSpawner
subclass (VariableSwamSpawner
) as a spawner class, with support forContainDSDashboard
.Below is the Dockerfile I use for my jupyterhub server:
Full environment
Configuration
Logs