The reportTimeout is based on when the request arrived. This was designed a couple of years ago and still works the same with no complaints so far. However, I understand this doesn't play so well with async requests.
We will reconsider this and come back shortly.
Thank you for the ideas.
The 4.10.1 including pdf utils fixes has been released
https://github.com/jsreport/jsreport/releases/tag/4.10.1
Great, thank you. I can replicate the problem.
Chrome has again changed how it is structuring the output PDF. We will need to adapt some parts.
Expecting to release hotfix 4.10.1 with the fix tomorrow.
I apologize for the inconvenience.
Feel free to post the details here or create a new post.
I've tried the exact steps from here
https://jsreport.net/learn/ubuntu
In a fresh Azure VM with Ubuntu 22.04 and I see no issues.
Could you isolate what you have different?
You may experience a wrong footer alignment issue when updating to jsreport 4.10.0 in case you use the CSS code from our samples or the studio pdf utils quick action to add header/footer. You will notice this visually when the footer is at the top and not at the bottom.
The reason for this is not the jsreport itself but the Chromium 138 dependency update, which changed the CSS flexbox engine calculation. This caused the CSS used in our demos to position the footer to the bottom to stop working.
Fortunately, the fix is easy.
Find the template you merge as the header/footer and locate the following CSS
.main {
....
height: 100%;
}
And change the 100% to 100vh
.main {
....
height: 100vh;
}
Could you share an example when the index gets broken in 4.10.0?
I don't see this problem in our samples.
Ok, I see. So you don't persist templates in the jsreport. Instead, you send anonymous templates to the report API, which includes the content and helpers.
Hm. It shouldn't happen that you get a response based on an older request. Likely, there is something wrong on your end.
Try to enable full profiling and check what is really the input and output at the jsreport side.
jsreport doesn't have a driver for ArangoDB, so how do you configure jsreport and persist templates?
Here are the docs for jsreport templates store drivers
https://jsreport.net/learn/template-stores
The thing is that this will likely have no implicit solution. Everyone will need to adapt the CSS.
We can't stick with old Chromium due to vulnerabilities, and this behavior is fully controlled by Chromium.
jsreport has no control over it.
We will check the table of contents demos...