Bug#1016732: [Pkg-javascript-devel] Bug#1016732: Please help to reproduce (Was: shiny-server: server-function? don't run)
On ഞാ, ഫെബ്രു 26 2023 at 02:33:31 രാവിലെ +05:30:00 +05:30:00, Pirate Praveen wrote: On ഞാ, ഫെബ്രു 26 2023 at 02:24:00 രാവിലെ +05:30:00 +05:30:00, Nilesh Patra wrote: On Sun, Feb 26, 2023 at 12:46:15AM +0530, Pirate Praveen wrote: Thanks for the pointer. However, unfortunately even after propagating the "-t" flag with coffee, the generated code does not work to fine (the UI is not functional). For now I have vendored coffee1 generated code itself. Do you have any other ideas? I can see we are using rollup to generate iife format files, which may not be what npm dist tarball ships. https://salsa.debian.org/js-team/node-sockjs/-/blob/master/debian/rules#L8 Upstream directly uses the output from coffee https://salsa.debian.org/js-team/node-sockjs/-/blob/master/Makefile#L9 You could play around with rollup output format options I think. Try umd format or try using webpack. You will have to inspect the npm dist tarball to see what format it has. Copying Akshay if he has some ideas. Since we are using only lib directory in node, ignore the rollup part above. In sockjs 0.4 rc1 they removed coffee script dependency, so one thing we can try is to see if sockjs 0.4 rc1 works with shiny-server, though getting a new upstream version to bookworm may be a hard thing, but it may be a better option that vendoring what we have right now.
Bug#1016732: Please help to reproduce (Was: shiny-server: server-function? don't run)
On ഞാ, ഫെബ്രു 26 2023 at 02:24:00 രാവിലെ +05:30:00 +05:30:00, Nilesh Patra wrote: On Sun, Feb 26, 2023 at 12:46:15AM +0530, Pirate Praveen wrote: Thanks for the pointer. However, unfortunately even after propagating the "-t" flag with coffee, the generated code does not work to fine (the UI is not functional). For now I have vendored coffee1 generated code itself. Do you have any other ideas? I can see we are using rollup to generate iife format files, which may not be what npm dist tarball ships. https://salsa.debian.org/js-team/node-sockjs/-/blob/master/debian/rules#L8 Upstream directly uses the output from coffee https://salsa.debian.org/js-team/node-sockjs/-/blob/master/Makefile#L9 You could play around with rollup output format options I think. Try umd format or try using webpack. You will have to inspect the npm dist tarball to see what format it has. Copying Akshay if he has some ideas.
Bug#1016732: Please help to reproduce (Was: shiny-server: server-function? don't run)
On Sun, Feb 26, 2023 at 12:46:15AM +0530, Pirate Praveen wrote: > On Sun, 12 Feb 2023 23:16:06 +0530 Nilesh Patra wrote: > > Sorry for pinging you again, but would you be able to take a look at this > please? > > I don't know enough coffeescript to be able to check this and it'd be > > awesome if you could consider taking a look. > > Coffeescript 2 creates ESM format js by default, adding -t option to coffee > command should give you the old ES5 javascript like coffeescript 1.x > > See https://salsa.debian.org/js-team/node-sockjs/-/blob/master/Makefile#L11 Thanks for the pointer. However, unfortunately even after propagating the "-t" flag with coffee, the generated code does not work to fine (the UI is not functional). For now I have vendored coffee1 generated code itself. Do you have any other ideas? -- Best, Nilesh signature.asc Description: PGP signature
Bug#1016732: Please help to reproduce (Was: shiny-server: server-function don't run)
On Sun, 12 Feb 2023 23:16:06 +0530 Nilesh Patra wrote: > Sorry for pinging you again, but would you be able to take a look at this please? > I don't know enough coffeescript to be able to check this and it'd be > awesome if you could consider taking a look. Coffeescript 2 creates ESM format js by default, adding -t option to coffee command should give you the old ES5 javascript like coffeescript 1.x See https://salsa.debian.org/js-team/node-sockjs/-/blob/master/Makefile#L11
Bug#1016732: Please help to reproduce (Was: shiny-server: server-function don't run)
Hi Yadd, On Sat, 28 Jan 2023 11:09:21 +0530 Nilesh Patra wrote: > On Fri, Jan 27, 2023 at 07:45:35PM +, Krüger, Sebastian wrote: > > I'm not a Shiny user either (so far), however the plan is for our institute > > to provide Shiny applications for certain users. (I will probably write > > some of these applications at some point, and I also administrate the web > > server...). > > > > My test system: I have a current Debian sid with R, cleaned from nodejs > > (apt...) and thus without shiny-server. > > > > Now I install the shiny-server (apt install shiny-server). > > > > In the packages r-cran-shiny and shiny-server are sample applications. I > > copied the examples from the r-cran-shiny package (e.g. > > /usr/lib/R/site-library/shiny/examples/01_hello) to /srv/shiny-server and > > could (after restarting shiny-server (systemctl restart shiny-server)) > > access the application via firefox: http://localhost:3838/01_hello/ . > > > > These applications consist of a UI part (user interface) and a result part. > > In the UI part, the web user can set (e.g.) parameters for the display in > > the result part. > > > > The problem: After installation, only the UI part is visible via the web > > browser. > > The result part is probably not visible because it does not receive any > > data from the UI part. > > > > With the help of a deb package for the Shiny sever from rstudio and the > > Debian package, I had at some point identified the sockjs installation as > > the problem... > > > > To get the Shiny application running (in the current scenario), I got the > > latest version of sockjs from github, "comped" it with npm () and then > > replaced the javascript files under "/usr/share/nodejs/sockjs/lib/" (from > > the Debian installation) with the files from the sockjs (github) package > > tree ".../node_modules/sockjs/lib/". > > > > After restarting the Shiny server, you can now also see the result part in > > the web browser and the Shiny application works. > > > > I am not a javascript/coffeescript friend or expert. The only thing I could > > see is that both my sockjs scripts and the Debian ones are based on the > > same github version > > (https://github.com/sockjs/sockjs-node/releases/tag/v0.3.24), but the > > Debian version was generated with coffescript 2.7.0 and "my" version was > > generated with coffescript 1.12.7. > > Looks like the coffeescript thingy in #1016732 is still unfixed and I've > re-opened the BR. Could you please > consider taking another look? Sorry for pinging you again, but would you be able to take a look at this please? I don't know enough coffeescript to be able to check this and it'd be awesome if you could consider taking a look. -- Best, Nilesh signature.asc Description: PGP signature
