search

jupyterhub / jupyter-rsession-proxy

Jupyter extensions for running an RStudio rsession proxy
BSD 3-Clause "New" or "Revised" License
118 stars 87 forks source link

GUI launcher won't show in jupyterlab #59

Open JBleher opened 5 years ago

JBleher commented 5 years ago

I have installed jupyter-rsession-proxy as set out in the documentation and the Dockerfile within a custom Dockerfile I created. (Basically, it combines R, Python, Julia and Octave and some extensions for the lab enviornment such as jupyterlab-latex and git. I am using the Dockerfile in a docker-deployed jupyterhub setting).

Since the major update and change of the package name a month ago, I am unable to get jupyter-rsession-proxy to work with jupyterlab (0.35). While in the classic notebook environment I get the RStudio entry in the menu and it works nicely, within jupyterlab there is no entry in the menu and there is no launcher...

When issuing jupyter labextensions list then I see that jupyterlab-server-proxy is installed.

I am not sure how to go about it. I would be happy to hear any advice

JBleher commented 5 years ago

So, I am not sure what happend. I thought the problem was a pip installation aside from the conda installation. It worked for the entire last week. That was the reason why I closed the issue.

However, since yesterday, when I had to rebuild the Dockerfile the launchers won't show in the jupyterlab environment. I really don't know how to approach this anymore. I can load the module jupyter_server_proxy module as well as the jupyster_rsession_proxy module in python in the container... in the classic notebook the menu shows just fine. I can open RStudio via classical notebook and adjusting the URL... /rstudio...

However, within the jupyterlab environment it does not work... any hints?

JBleher commented 5 years ago

This is indeed a browser issue. Just saw the reference to @vnijs' issue. Icons are not displayed in Firefox 60.0.5 but in Firefox 64 or later they work perfectly.

Also Chromium 71.0 does not have a problem.

For Edge 42.17 with EdgeHTML 17.17134, it also is a problem. Some of the later versions work. Haven't tried all of them... the current version 44. or so with EdgeHTML 18. is fine.

So it seems this is a browser version issue.