-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Runtime Error: maximum recursion depth #114
Comments
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗 |
This also makes me suspect that the problem is related to the NativeAuth module |
I also had this problem on two instances of jupyterhub with nativeauthentificator (Sometimes with few users and in less than a week). |
It seems to be caused by the jinja |
The env.loader was replaced by a new ChoiceLoader wrapping the previous loader on every render. It seems that the `_loaded` attribute was here to avoid re-registering the loader but it was set to `True` on the handler instance and not on its class making it useless since the a handler instance is created for each request. Closes jupyterhub#114.
This bug can be easily reproduced by sending a lot of requests to the /hub/login page. while true; do $JUPYTERHUB_BASE_URL/hub/login -s > /dev/null; done It starts to crash after around 10 seconds on my machine. |
The env.loader was replaced by a new ChoiceLoader wrapping the previous loader on every render. It seems that the `_loaded` attribute was here to avoid re-registering the loader but it was set to `True` on the handler instance and not on its class making it useless since the a handler instance is created for each request. Closes jupyterhub#114.
The env.loader was replaced by a new ChoiceLoader wrapping the previous loader on every render. It seems that the `_loaded` attribute was here to avoid re-registering the loader but it was set to `True` on the handler instance and not on its class making it useless since the a handler instance is created for each request. Closes jupyterhub#114.
Bug description
I have a Jupyterhub configured to use Native Auth, with DockerSpawner.
After running for a while (months or weeks, a time which I suspect depends on how many users are active), the server experiences a runtime error
RecursionError: maximum recursion depth exceeded while calling a Python object
Expected behaviour
I would expect that it would just run.
Actual behaviour
After some period of time, it triggers runtime errors:
Looking in the error message output, it seems that this might be related to the Native Auth authenticator:
In particular, I am suspicious that this may be triggered by the line:
After this initial error message, the logfiles are filled with tracebacks like this one:
How to reproduce
Your personal set up
Linux
jupyterhub version 1.0.0
Dockerspawner
The text was updated successfully, but these errors were encountered: