@bjrmatos and @jan_blaha is there any update on this issue and version 2.6.0?
AB-D
@AB-D
0
Reputation
23
Posts
199
Profile views
0
Followers
0
Following
Posts made by AB-D
-
RE: Protocol error (Page.printToPDF): Target closed.posted in general forum
-
RE: Protocol error (Page.printToPDF): Target closed.posted in general forum
Hi @jan_blaha do you have any update on this issue and version 2.6.0?
-
RE: Protocol error (Page.printToPDF): Target closed.posted in general forum
We use docker as well.
We cannot move past version 2.4.0.
Our entire setup works using 2.4.0, but the minute that we update to 2.5.0 we get these errors.
I am not sure how we can make a replicable demo to show you. It can't be replicated in the playground.
-
Getting complete logs when using chrome-pdfposted in general forum
Hi,
It is sometimes important for me to get logs when using chrome-pdf, the only way that I can access the logs is through the studio startup page, however it is often cut off. How do I get the complete logs. See log is cut off at +938
I have tried to wait for the printing trigger.
Thank you.
-
RE: Protocol error (Page.printToPDF): Target closed.posted in general forum
Hi, just refining the question here.
If I run the template in version 2.5.0 i get this error:
Protocol error (Runtime.callFunctionOn): Target closed.
Error: Protocol error (Runtime.callFunctionOn): Target closed. at Promise (/app/node_modules/puppeteer/lib/Connection.js:183:56) at new Promise () at CDPSession.send (/app/node_modules/puppeteer/lib/Connection.js:182:12) at JSHandle.jsonValue (/app/node_modules/puppeteer/lib/JSHandle.js:87:43) at JSHandle. (/app/node_modules/puppeteer/lib/helper.js:111:23) at ExecutionContext.evaluate (/app/node_modules/puppeteer/lib/ExecutionContext.js:49:33) at at process._tickDomainCallback (internal/process/next_tick.js:229:7) -- ASYNC -- at ExecutionContext. (/app/node_modules/puppeteer/lib/helper.js:110:27) at DOMWorld.evaluate (/app/node_modules/puppeteer/lib/DOMWorld.js:112:20) at at process._tickDomainCallback (internal/process/next_tick.js:229:7) -- ASYNC -- at Frame. (/app/node_modules/puppeteer/lib/helper.js:110:27) at Page.evaluate (/app/node_modules/puppeteer/lib/Page.js:782:43) at Page. (/app/node_modules/puppeteer/lib/helper.js:111:23) at runWithTimeout (/app/node_modules/chrome-page-eval/lib/eval.js:179:39) at at process._tickDomainCallback (internal/process/next_tick.js:229:7)+0 Starting rendering request 823 (user: reports)
+3 Rendering template { name: excelTables, recipe: html-to-xlsx, engine: handlebars, preview: true }
+7 Adding sample data BkxQsl9E1B
+12 Resources not defined for this template.
+15 Base url not specified, skipping its injection.
+15 Rendering engine handlebars
+35 Taking compiled template from engine cache
+50 Executing recipe html-to-xlsxIf I roll the server back to version 2.3.0 and run the exact same template then it works.
Currently I am not able to use version 2.5.0 because of these errors.
-
RE: Protocol error (Page.printToPDF): Target closed.posted in general forum
Hi, I should probably emphasise that this error only arises after updating to 2.5.0
If I run the exact same template and the exact same data in an earlier version I do not get this error.
-
RE: Protocol error (Page.printToPDF): Target closed.posted in general forum
Hmm, looking again it seems to be an issue with the amount of data that I am sending to the report (and therefore the amount of pages).
Usually I would get a timeout error if there were too many pages, but not it looks like I get this. Does that sound right?
-
Protocol error (Page.printToPDF): Target closed.posted in general forum
I Seem to be getting this error quite a lot after updating to version 2.5.0:
Protocol error (Page.printToPDF): Target closed.
Error: Protocol error (Page.printToPDF): Target closed. at Promise (/app/node_modules/puppeteer/lib/Connection.js:183:56) at new Promise () at CDPSession.send (/app/node_modules/puppeteer/lib/Connection.js:182:12) at Page.pdf (/app/node_modules/puppeteer/lib/Page.js:926:39) at Page. (/app/node_modules/puppeteer/lib/helper.js:111:23) at runWithTimeout (/app/node_modules/jsreport-chrome-pdf/lib/conversion.js:164:27) at at process._tickDomainCallback (internal/process/next_tick.js:229:7)Is there any advice to how to stop it, or what is causing it?
-
RE: Loading external libraries in scripts using docxtemplater recipeposted in general forum
Great, thanks. That was easy.
Cheers.
-
Loading external libraries in scripts using docxtemplater recipeposted in general forum
Hi,
I have been using chrome-pdf and html-to-xlsx recipes with success, each template uses moment.js. In each template have just loaded moment.js in <script> tags in the <head> section of the template. This has worked well to make the moment.js library available to the template and the functions that are called in the template.
Now I am using docxtemplater, which has a blank template. I need to use a script to manipulate the data. What is the best way to make the moment.js library available within this script?
Cheers.