Skip to content
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

Issues with jinja2_env #355

Closed
camer314 opened this issue Apr 17, 2021 · 1 comment
Closed

Issues with jinja2_env #355

camer314 opened this issue Apr 17, 2021 · 1 comment

Comments

@camer314
Copy link

camer314 commented Apr 17, 2021

I have been using the @jupyterhub\services JavaScript SDK to communicate with kernels by starting a notebook.

I was reading about the kernel gateway which is an alternate way to access kernels without a UI, which seems perfect. However I installed the latest kernel_gateway (2.4.3) and straight away am receiving the below error which renders the gateway inoperable.

There seems to be some history with this error (#71) and (#99) but these are both from 2016.

Is this a recurrence of the issue or has it never been fixed?

[I 210417 15:35:47 web:2243] 200 GET /api/kernels?1618637747393 (127.0.0.1) 0.00ms
[E 210417 15:35:47 web:1219] Uncaught exception in write_error
Traceback (most recent call last):
File "c:\users\camer314\appdata\local\continuum\anaconda3\envs\azureml\lib\site-packages\tornado\web.py", line 1217, in send_error
self.write_error(status_code, **kwargs)
File "c:\users\camer314\appdata\local\continuum\anaconda3\envs\azureml\lib\site-packages\notebook\base\handlers.py", line 585, in write_error
html = self.render_template('%s.html' % status_code, **ns)
File "c:\users\camer314\appdata\local\continuum\anaconda3\envs\azureml\lib\site-packages\notebook\base\handlers.py", line 515, in render_template
template = self.get_template(name)
File "c:\users\camer314\appdata\local\continuum\anaconda3\envs\azureml\lib\site-packages\notebook\base\handlers.py", line 511, in get_template
return self.settings['jinja2_env'].get_template(name)
KeyError: 'jinja2_env'

@camer314
Copy link
Author

Actually having read this [(https://github.com//issues/233)] it gave me a clue that for tokens the WS must receive them as a query parameter so I modified my server connection object to honour that and now its working as expected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant