-
Notifications
You must be signed in to change notification settings - Fork 86
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
"No user specified" error with Rstudio 1.2.1335 #65
Comments
RStudio 1.2.1335 requires a header "X-RStudioUserIdentity" with the username, according to https://github.com/rstudio/rstudio/blame/8af730409bb6d651cc8f6816d136bea91441e7a4/src/cpp/server_core/sessions/SessionSignature.cpp#L30-L43 (I wish I knew how to pass this header from the jupyterhub rsession proxy) |
I believe overriding proxy_request_headers will work here. If nobody gets to this before me I'll try to work on it next week. A better solution would be to make this independent of the http client we happen to be using now. |
I've prepared a fix for this which involves letting jupyter-server-proxy users specify additional headers. However I then tried to reproduce this issue without the fix and was unable to do so. I was able to execute commands from Console and by hitting Run from within an editor. Do you have some tips on how to reproduce? Here is the container I was testing from which uses jupyter-server-proxy master and jupyter-rsession-proxy master:
Iirc there's another server extension which wants the additional headers feature so I'll work on it regardless. |
Thanks! I'll test as soon as I can, hopefully this week or the next one. I will try to provide a small reproducible environment as well. With respect to the reproducible environment, it is a bit confusing to me that the latest jupyter-rsesion-proxy version on pypi is (apparently?) not merged #57 ... Do you know why? |
Not sure why that PR hasn't merged yet. Maybe its worthwhile to post a message on that issue? Fwiw, I tried using the desktop version of rstudio rather than rstudio-server in the same Dockerfile as above and it also ran fine. |
I am puzzled since I can't reproduce the error anymore. Maybe @anton-khodak can? On the other hand, I realized I was getting all sorts of errors from RStudio due to So maybe the "No user specified" error was actually related to that and I fixed it. RStudio is working fine now for me as well with the current pypi versions. In case Anton can reproduce the issue, maybe he can also check if it is solved by setting proper permissions in his rstudio directory. To address a), I created this script: #!/bin/sh
# Name it fix-rstudio.sh and place it with your notebook Dockerfile
chown -R ${NB_UID}:${NB_GID} /home/${NB_USER}/.rstudio And add it to the COPY fix-rstudio.sh /usr/local/bin/before-notebook.d/fix-rstudio.sh To address b), I made sure the |
Sorry for taking so long to answer. A reproducible example would be to use @ryanlovett 's Dockerfile and to try running a chunk in a file with a name "test.Rmd" and content
The error message in the console is:
|
I was able to reproduce the error. I had to add a lot more packages to get Seurat to install (new Dockerfile below) -- I didn't experiment with others. I'll see if the configurable_headers stuff I worked on earlier fixes it.
|
Hi. I am seeing this same issue also using 1.2.5033. Easiest test case to reproduce is: @ryanlovett Can I test your fix for this one? simplest.Rmd:
|
I tried to hardcode the header in _build_proxy_request handlers.py of jupyter server proxy but not working....
|
Not sure what is going on here. Updated the nginx ingress to always send the X-RStudioUserIdentity header with value of jovyan but it did not help. I can see that it is set from the logs of the user image but I still get the ERROR system error 13 (Permission denied) [description=No user specified] |
@scivm My changes were in branches of both jupyter-rsession-proxy and jupyter-server-proxy: master...ryanlovett:proxy_headers jupyterhub/jupyter-server-proxy@master...ryanlovett:configurable_headers |
Hi,
I'm using jupyter-rsession-proxy inside zero-to-jupyterhub Kubernetes deployment. For Rstudio version == 1.2.1335 R code is executed in console, but launching any R code from the editor ends with an error:
It works as expected with RStudio == 1.1.456. I suspect it has something to deal with how rsession-proxy specifies a user when starting Rstudio.
The text was updated successfully, but these errors were encountered: