-
Notifications
You must be signed in to change notification settings - Fork 5
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
Cannot get this working #19
Comments
If I install 0.2.0a2 I seem to get something working. But I get the error below in the console [E 2021-07-31 19:04:46.397 ServerApp] Uncaught exception GET /server-proxy/icon/panel (172.17.0.1)
HTTPServerRequest(protocol='http', host='localhost:8889', method='GET', uri='/server-proxy/icon/panel', version='HTTP/1.1', remote_ip='172.17.0.1')
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/tornado/web.py", line 1704, in _execute
result = await result
File "/usr/local/lib/python3.7/site-packages/jupyter_server_proxy/api.py", line 68, in get
with open(self.icons[name]) as f:
FileNotFoundError: [Errno 2] No such file or directory: '/usr/local/lib/python3.7/site-packages/panel_server/icons/logo.svg' My setup is here https://github.com/MarcSkovMadsen/awesome-panel-introduction/blob/144631113e539cbd6c63ac7e5c68b079456528c1/jupyter-panel-proxy.yml. I'm running it from this Docker image https://github.com/MarcSkovMadsen/awesome-panel-introduction/blob/144631113e539cbd6c63ac7e5c68b079456528c1/Dockerfile.jupyter |
Now I moved to binder and I managed to get something working. Check out https://mybinder.org/v2/gh/marcskovmadsen/awesome-panel-introduction/main?urlpath=panel/introduction |
If you open jupyter lab you https://mybinder.org/v2/gh/marcskovmadsen/awesome-panel-introduction/main?urlpath=lab/tree/presentation you will see the missing logo But when I click the button it still works as expected and looks nice |
I simply cannot get this working.
I've realized its probably because the README has been updated without the package being released.
The text was updated successfully, but these errors were encountered: