-
Notifications
You must be signed in to change notification settings - Fork 87
Incompatible with jupyter-labhub
#235
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
Comments
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗 |
Just as a hint/comment: Copying the (missing) status.html solves the problem temporary. In detail I had to run |
Anyone an idea how to fix that? |
@fritterhoff what version of nbgitpuller are you using? We fixed this for v1.0 I think. |
Hi @yuvipanda |
This bug is reproducible with this docker image |
Could you both show us your full JupyterHub configuration with secrets redacted, and also show the output of |
@manics Well that could get complicated as I use it via zero-to-jupyterhub-k8s ... |
So I'm able to provide some instructions to reproduce the bug:
or even more simple:
|
@fritterhoff thanks for digging into the problem, and providing a minimal example! It looks like there's a mix of notebook and jupyter-server, I think this should fix it: |
#240 does indeed seem to fix this in my case. Thank you! |
I ran into this today and tried to install nbgitpuller from https://github.com/manics/nbgitpuller/tree/jupyter-server but didn't fix the issue. Debugging locally I get the same error: ServerApp - ERROR - Uncaught exception GET /git-pull?repo=https%3A%2F%2Fgithub.com%2FNASA-Openscapes%2Fearthdata-cloud-cookbook&urlpath=lab%2Ftree%2Fearthdata-cloud-cookbook%2Fexamples%2F&branch=ux-exercise (172.17.0.1)
HTTPServerRequest(protocol='http', host='127.0.0.1:8888', method='GET', uri='/git-pull?repo=https%3A%2F%2Fgithub.com%2FNASA-Openscapes%2Fearthdata-cloud-cookbook&urlpath=lab%2Ftree%2Fearthdata-cloud-cookbook%2Fexamples%2F&branch=ux-exercise', version='HTTP/1.1', remote_ip='172.17.0.1')
Traceback (most recent call last):
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/tornado/web.py", line 1704, in _execute
result = await result
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/tornado/gen.py", line 216, in wrapper
result = ctx_run(func, *args, **kwargs)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/nbgitpuller/handlers.py", line 175, in get
self.render_template(
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/notebook/base/handlers.py", line 515, in render_template
template = self.get_template(name)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/nbclassic/nbserver.py", line 140, in get_template
return self.settings['notebook_jinja2_env'].get_template(name)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/jinja2/environment.py", line 997, in get_template
return self._load_template(name, globals)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/jinja2/environment.py", line 958, in _load_template
template = self.loader.load(self, name, self.make_globals(globals))
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/jinja2/loaders.py", line 125, in load
source, filename, uptodate = self.get_source(environment, name)
File "/srv/conda/envs/notebook/lib/python3.9/site-packages/jinja2/loaders.py", line 214, in get_source
raise TemplateNotFound(template)
jinja2.exceptions.TemplateNotFound: status.html
|
- Our template loader setup was a hack, and that hack seems to have stopped working. - We just use our own loader instead. This means we lose the base translation functionality of upstream render_template - but we were not using it at all anyway, so 'tis alright. - Looks like the path for the stylesheet we were 'borrowing' from classic notebook changed location, so update to use the new location. This will stop existing after notebook v7, and we will need to use our own. Fixes jupyterhub#235
Currently, our "Launch in Hub" button is throwing a 500 error, possibly because of jupyterhub/nbgitpuller#235. This updates nbgitpuller to a version with a fix for that issue.
Currently, our "Launch in Hub" button is throwing a 500 error, possibly because of jupyterhub/nbgitpuller#235. This updates nbgitpuller to a version with a fix for that issue.
Bug description
As soon as I try to use a nbgitpuller Link with the
jupyter-labhub
Backend I only get a "Internal Server Error" and some errors in the logs. Using the "normal" backend works fine.Expected behaviour
Normal cloning of the repo.
Actual behaviour
HTTP Status 500
How to reproduce
Start single user nb with
jupyter-labhub
and try to open a nbgitpuller linkYour personal set up
Logs
The text was updated successfully, but these errors were encountered: