-
Notifications
You must be signed in to change notification settings - Fork 60
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
ProfilesSpawner stops Jupyterhub from recognizing running worker #41
Comments
@Hoeze in your logs I don't see something like
That's when |
Thanks for your answer @rcthomas. I moved the import to the end but this does not change anything. Could this be a problem with Logs:
|
@rcthomas Here is a minimal example configuration that does not work:
This has no user authentication, etc. At least this minimal example should work out-of-the-box, right? |
This goes away if I specify An even more minimal reproducer is just:
|
Full details. I tested by building this Dockerfile. To make it fail, take out
For the config it's just
|
Thank you so much @rcthomas! |
Is there somewhere I can see the logs for wrapspawner? I'd like to track down a fix for this. Can't seem to find them on the client or the hub - if possible I'd like to use traitlets v5 as it's causing issues with other packages to downgrade to 4. |
@hakasapl it would normally be in the regular JupyterHub log output. But if you look in wrapspawner you'll see that there are no log messages coming from it. Since traitlets<5 is working just fine for me I was going to let this slide till I absolutely had to do anything about it or it got fixed. My brilliant plan for that day was to add logging messages and trace through wrapspawner and hub code. Maybe you'll give that a shot? Does the reproducer work for you? |
Sounds good, I'll try to add some debug messages and see where I get. The main issue I'm running into is that conda doesn't let me install both traitlets<5 and python 3.9 - 3.8 works fine, so it's fine for now, but may present an issue in the near future. I believe PyPi doesn't have this issue, you can install traitlets<5 and python 3.9. |
Finally was able to get enough time to look at this. What is happening is that something has changed in traitlets 4 to traitlets 5 where
Under traitlets 4.3.3 this is a long list of things, under traitlets 5.0.5 it's much smaller (basically only stuff passed to the constructor, plus I traced through the last few years of changes in traitlets. One of the things that I noticed is that along the way was this accepted MR which adds a less private-looking I've tested this on the reproducer, and I'm going to come up with a PR that at least allows for the old behavior on traitlets 4 but uses this method with traitlets 5. We could try getting that second term of the computation more right for traitlets 4. Stay tuned. |
This issue has been mentioned on Jupyter Community Forum. There might be relevant details there: |
Hi @rcthomas, is this issue solved as of today? |
@Hoeze the part about about https://github.com/jupyterhub/wrapspawner/releases/tag/v1.0.1 So I think the traitlets-related part of this is fixed with that release. |
Hi, apologies for the double post, I moved this issue from jupyterhub/batchspawner#194.
We currently cannot spawn any workers with ProfilesSpawner enabled.
The worker starts normally but the jupyterhub directly kills it.
Logs of the worker:
Logs of jupyterhub:
I am using python 3.7, jupyterhub 1.2, batchspawner 1.0.1 and the current git version of wrapspawner.
When directly applying batchspawner, everything is working fine.
My configuration to reproduce:
The text was updated successfully, but these errors were encountered: