You can use
reportTimeout config, set the number of ms there, and pass it to the azure web app as an environment variable.
This can be done in the azure portal / web app / application settings.
Posts made by jan_blaha
RE: Extending timeout - docker
You can use
RE: jsreport-dotnet-example-webapp-master example code runtime error ...
Hm, maybe an antivirus is blocking the chrome executable.
Please try to change the line here.
Does it help?
Could you try to install full jsreport and render a pdf there? It's typically easier to troubleshoot there the first.
RE: PDF password protection via pdf-utils
thank you for the bug report. Two problems here.
The first is that the enum has values
notAllowed, highResolution, lowResolution
The second problem is that we recently fixed a bug in the password protection which will be part of the next release jsreport 2.11. This should be released in the next few days. In summary, please wait for the 2.11 and use
RE: Blank pdf output
Maybe please delete or answer your duplicated question here
RE: slow performance - timeout on 1000+ records
The performance and render time is based mainly on the report js/css/html complexity. You can render 1000pages in 3seconds but it can also take 3 minutes.
Try to increase the timeout (
cfg.ReportTimeout) and see how it actually takes.
It could also help to check the logs, where is the rendering stuck. This is typically in the chrome-pdf html->pdf conversion, but I may be wrong.
RE: Deploy jsreport into firebase function as an existing Node.js project.
I see. Does it provide a temp where you can write? I guess you can reach the same problems when running the AWS Lambda function.
Please try to read through the tutorial here
In particular, check this config which disables writing to logs or redirects the writes to the temp
RE: How to buy a validated P12 cert?
How do I get hold of a trusted certificate for this use? Our regular SSL cert for the server API is issued by Amazon. I don't think they'll issue anything else but certificates for the domains we have registered with them.
I don't have any experience here. I see here some notes and option to purchase but haven't tried it
I'm busy now to try this out, but if you go through the process, please write down notes and share it.
We will happily add it to the documentation then.
When problem 1 is solved: How do I embed enough information in the PDF so the verification can be done even after the certificate has expired? See "Establish long-term signature validation" at the following link:
It seems the long term validation is enabled by default. Am I missing something?