It's definitely an issue with jsreports to chromium, but i don't know what it would be. If i run my docker to a bash shell and then execute

/app-rprt$ /usr/bin/chromium-browser --no-sandbox --disable-dev-shm-usage --headless --disable-gpu --print-to-pdf $1

it generates output.pdf with content in it. This is the output though.

[0322/121710.387637:ERROR:bus.cc(399)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[0322/121710.391744:ERROR:bus.cc(399)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[0322/121710.391805:ERROR:bus.cc(399)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[0322/121710.400029:WARNING:bluez_dbus_manager.cc(247)] Floss manager not present, cannot set Floss enable/disable.
[0322/121710.441692:WARNING:sandbox_linux.cc(393)] InitializeSandbox() called with multiple threads in process gpu-process.
659 bytes written to file output.pdf

Not sure if that matters or not in what you guys are doing with the return. I did not run your docker to see what the output looks like on your side. Could you please let me know if you think this is the issue?

We don't do anything with OracleDB, so i am assuming i don't need anything with that section.

We had this in there from before. Not sure if it's needed or not:

WORKDIR /${APPDIR}
# the chrome was already installed from apt-get
ENV PUPPETEER_SKIP_CHROMIUM_DOWNLOAD true
ENV NODE_OPTIONS "--openssl-legacy-provider"

RUN npm install -g @jsreport/jsreport-cli
RUNN npm install -g @jsreport/jsreport-unoconv

RUN jsreport init

We use elasticSearch in our for logging, so i have

RUN npm install --save winston winston-elasticsearch

We have a couple more NPM packages

RUN npm install --save chart.js
RUN npm install --save request

I also have a couple of extra lines at the bottom that we may not need:

ENV PATH "$PATH:/fop-2.1"
ENV NODE_ENV production
#ENV chrome_launchOptions_executablePath /usr/bin/chromium-browser
ENV chrome_launchOptions_args --no-sandbox,--disable-dev-shm-usage

Everything else lines up. The versions all match for NPM packages. Anything else that's in our dockerfile are AWS specific for our hosting

We upgraded to the latest version to test with and it won't render any of our PDFs. To be sure, we took an export of https://playground.jsreport.net/w/admin/hBfqC7af and imported it in to our environment and it just hangs at "Executing recipe chrome-pdf". If we run this same thing on 4.2 we do not have any issues. We did not change our docker at all except to install the new version so it's still got this line in it for Chrome:
apt install -y chromium-browser=112.0.5615.49-0ubuntu0.18.04.1 chromium-codecs-ffmpeg=112.0.5615.49-0ubuntu0.18.04.1 && \

We updated to 4.0 and we are getting weird behavior with checkboxes when trying to export. We have lots of folders and on average about 6 files per folder. When I right click on a folder in Studio and click Export Folder, it brings up a dialog with the folder and all files selected. If i try to change checkboxes, it selects different files. This is making the export difficult to select what we want and move those files over to our production setup

You can see this behavior here:

https://www.flexclip.com/share/38848218a5d023d4e961062aa32c703c6c4b3e3.html

I was wondering if you guys have done anything with the Office Online Server to be able to have a private server for office preview. I know you have configuration on where to store the files (on our server vs. yours), but what about being able to change the actual previewing server from MS's public server to using Office Online Server which is free if you want to be able to have it in read-only mode. I am looking at trying to set up a proof of concept server to be able to preview documents internally on our servers for a secured site and I would love the ability to be able to offer the same through JSReport templates that we have already setup.

Thanks,
Justin

For our stuff, it was because the SUM() formula that was in our template file referenced a cell that was below it. We actually didn't modify anything via code in the xlsx recipe and just put in the xslxPrint command and it threw that error, so it's validating things that aren't even touching. Excel had no problem with the forumla using a cell below what was being summed, but JSReport did. So we had to rip out the formula and manually calculate it ourself and then put the Replace command in there to write the value instead of the formula

as an FYI, we ran in to the same issue and had to code around it. It seems more checking was added to make sure things didn't go out of bounds and changing the order to make sure the cells were created before this was done was our only solution. Sort of a pain, but it did work for us

That's fantastic news. Thanks for digging in to this as i know it wasn't easy to find and fix. Hopefully the performance improvements will be a benefit to everyone. I know they will be huge for us and save us from having to rewrite a bunch of reports using a non-standard way.

Checking on status. Have you found the underlying cause of the slowness?

I may not be describing things correctly, but i am trying to access variables from within helpers, not scripts. Does that matter?

I will work on getting you a playground entry to look at so you can see, but if the helpers can't run the beforeRender and don't have access to variables within the global, it won't really matter much