I think maybe that’s an issue from the “proxy” side since I just figured out Shiny is waiting for the proxy to create the socket.
Is there anything I can do to know if the lua-resty-session works properly?
The app seems just an example, not sure if that’s supposed to work out of the box or it needs more adjustments.
Does anyone have a working example of shiny app?
Unfortunately I wasn’t able to replicate this. For the lua-resty-session, I would see if you can find something in the logs, but other than that I don’t know how else you could test the session working properly.
I’m able to reproduce the error that @fenz reports. It is occurring for R versions 4.0.x, x = 0-5.
versions 3 work fine. This bug report seems to be relevant:
Thanks for your reply.
I actually get the same issue on both R 4.0.3 and R 3.6.3. I just checked the modules I have access to on the system and the configuration is:
R-4.0.3> packageVersion("shiny")
[1] ‘1.4.0.2’
R-3.6.3> packageVersion("shiny")
[1] ‘1.5.0’
So in my modules the newer R has an older shiny package but, in both cases, older than version “1.5.3.1” (mentioned in the issue linked).
Can you tell me the versions of both R and shiny which work for you?
Many thanks for your help!
So, following @dugan info, I run shiny in a container instead of using the one from the R module.
I can confirm this image: rocker/shiny:3.6.2 still works.
But it seems newer versions fail.