Posts made by jitendra5792

Why don’t the other properties, like pdf margin top, get applied to this PDF?

I am unable to print a web page to PDF.

I want to convert https://tomastrajan.github.io/angular-ngrx-material-starter#/examples/stock-market to PDF. But it should wait for the page to complete visually. and then start the PDF generation. But seems it is not working.

Tried the following approach, but it times out.

Template:

Script:

Getting the following issue on reverting uncommitted changes. We are using MongoDB storage.
Any suggestions to troubleshoot this?

MongoServerError: Updating the path '@odata' would create a conflict at '@odata' at UpdateManyOperation.execute (/app/node_modules/mongodb/lib/operations/update.js:101:19) at process.processTicksAndRejections (node:internal/process/task_queues:105:5) at async tryOperation (/app/node_modules/mongodb/lib/operations/execute_operation.js:203:20) at async executeOperation (/app/node_modules/mongodb/lib/operations/execute_operation.js:73:16) at async Collection.updateMany (/app/node_modules/mongodb/lib/collection.js:231:16) at async Object.update (/app/node_modules/@jsreport/jsreport-mongodb-store/lib/provider.js:236:19) at async persistChanges (/app/node_modules/@jsreport/jsreport-version-control/lib/main/versionControl.js:172:29)...

Thanks very much!

We are currently using async reports and sending multiple asynchronous requests to jsreport. As expected, jsreport adds these requests to its queue.

We’ve configured the reportTimeout setting to 45 minutes. However, we’ve observed that the timeout countdown begins as soon as the request reaches jsreport — not when the actual report execution starts.

Ideally, we were expecting the reportTimeout to start only once the report begins execution, rather than from the time it enters the queue. Could you please confirm if this is the intended behavior? If so, is there a recommended approach to handle longer queue times without prematurely triggering the timeout?

These async reports, as well as others in the queue, failed due to the 45-minute timeout being reached. The delay was caused by earlier async reports that were still pending in the queue.

Yes MS Excel in Windows.

I understand that browser preview is a black box.

But the following screenshot is from the Excel that I created manually on my PC. In that the complete text is visible.

But the file that is generated using jsreport does not show the complete text.

If we create an Excel manually on our PC with the same content, in that case, the behaviour is the same, like if the rest of the cells are empty, the complete text is visible.

It is when the file is generated using jsreport with same text width and cell content, the text is not visible. What could be the cause?

https://playground.jsreport.net/w/anon/oC498X3B

We are using html-to-xlsx recipe with cheerio.

Please refer to this workspace.
When I view the preview in jsreport, the text in the first cell is visible as a whole even if the cell width is less and the content is exceeding. Because the next cells are empty.

But as soon as I download the file and open in Excel, it does not show as a whole text. It shows truncated:

We tried generating PDF report with more than 80K rows on a Windows machine after setting it up following the steps: https://jsreport.net/on-prem (without any docker image)

The RAM consumption for 1 lakh rows was around 11 GB, but it generated the report successfully with div (We removed the table tags and created a div structure for the tabular report).

But in the containerised K8s environment, we get the following error:

We need to generate a 100k-row PDF report, and we want to do it with jsreport deployed in a containerised environment. Can you please suggest what we should do to overcome the error we are facing?

If we deploy it on a standalone VM, it works fine to generate the report.

This is a blocker for us.

Can you please suggest a solution? We suspect some issue around the puppeteer/chromium in the base image. We are using this base image - FROM jsreport/jsreport:4.7.0-full.