Update jupyterhub pinning to >=5.2.0,<6 from ==5.1.0 #1008
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Something is wrong
It seems that starting the server leads to 500 error:
JupyterHub 5.2.0 logs on server spawn
Investigation
With jupyterhub/jupyterhub#4904, the Spawner base class had its
env_keep
default value changed, to for example not includePATH
. The default value of LocalProcessSpawner was unchanged, but SystemdSpawner used by tljh inherits from Spawner, so it has been impacted.I'm not confident on whats a sufficient fix yet, or where - it could be systemdspawner, tljh, or jupyterhub.
I think its systemdspawner to begin with, because I think its test suite would fail if
SystemdSpawner.extra_paths
where configured when used against jupyterhub 5.2.0, which it isn't in the test suite, but extra_paths is configured by tljh.I've opened jupyterhub/systemdspawner#144 so far about this, and have tried it in 2cb3bab.