We have one test server and 5 production servers.
Deleting all of the files on the test server and importing them fresh seemed to help, and it does not timeout.
I don't want to do that on the production servers though, incase I am unable to upload them again. The production servers are the ones that will generate the timeout error but will usually update in an hour or so (most of the time, sometimes they don't).
It is blob storage.
And yes it works better if the import file is smaller - I cleaned out some unneeded test data and got the import file down to 8.3MB and it will update but the behaviour is not good.
If I upload the file and wait for the process to complete there will be a pop up like this:
But if I come back to that server in 2 hours - it will say that all of the files were updated 2 hours ago.
We were on 4.3 before and we just updated to 4.9. 4.3 did not have any upload issues like this, even when the import file was much bigger - around 20MB.
Hi, we have recently updated to 4.9.0 and we are now getting this error when attempting a full import objects.
Error: Timeout during waiting for file system, try it again later.
at Object.rejectItemsWithTimeout (/app/node_modules/@jsreport/jsreport-fs-store/lib/queue.js:52:23)
at Timeout._onTimeout (/app/node_modules/@jsreport/jsreport-fs-store/lib/transaction.js:76:11)
at listOnTimeout (node:internal/timers:588:17)
at process.processTimers (node:internal/timers:523:7)... Error: Error: Timeout during waiting for file system, try it again later.
at Object.rejectItemsWithTimeout (/app/node_modules/@jsreport/jsreport-fs-store/lib/queue.js:52:23)
at Timeout._onTimeout (/app/node_modules/@jsreport/jsreport-fs-store/lib/transaction.js:76:11)
at listOnTimeout (node:internal/timers:588:17)
at process.processTimers (node:internal/timers:523:7)...
at https://x20-reports-prod-au2.azurewebsites.net/studio/assets/client.aad5b26fb7f7c29c0340.js:2:372044
at https://x20-reports-prod-au2.azurewebsites.net/studio/assets/client.aad5b26fb7f7c29c0340.js:2:372113
at b.callback (https://x20-reports-prod-au2.azurewebsites.net/studio/assets/client.aad5b26fb7f7c29c0340.js:2:4565694)
at b.<anonymous> (https://x20-reports-prod-au2.azurewebsites.net/studio/assets/client.aad5b26fb7f7c29c0340.js:2:4563670)
at t.emit (https://x20-reports-prod-au2.azurewebsites.net/studio/assets/client.aad5b26fb7f7c29c0340.js:2:426013)
at t.onreadystatechange (https://x20-reports-prod-au2.azurewebsites.net/studio/assets/client.aad5b26fb7f7c29c0340.js:2:4567387)
We have a custom docker image hosted in our container registry and served from an Azure app service.
Hi, we are going to update our test and production servers to the latest version, however when I initialise the latest version "start" is not there.
(Also, I used to be able to post pictures when I made a post but it says that I don't have the privileges to do that anymore - here is the text)
Ok, so update:
The file is now working if i use this syntax:
{{#xlsxReplace "xl/styles.xml"}}
{#asset style.xml}
{{/xlsxReplace}}
Just removing the extra curly bracket at the end, the file now works locally, and on the test server.
However, virtually identical files with the extra curly bracket will also work.
It also does not explain why the same file was working locally but not on the test server
Regarding the typo...
This does seem to be a problem. I have one report that uses it and runs perfectly:
This one will run every time:
But this one will not:
Unless you remove that replace code:
But then the files need to be "repaired" because they are not styled properly and are not suitable for client use.
The exact syntax for that replace code I got from here:
I thought it was a typo but it turns out that the stackoverflow poster got it right, and this looks like the only way to replace a style file.
Hi Jan,
Yes, I have to include that typo - the style file will not apply unless it is types exactly like that - can you tell me how what the exact syntax should be?
The issue is that the exact same file will work on one environment but not the other - even with that typo, also, I can't send you the export for commercial reasons. But even if I did, you could get the same issue, that it will work locally but not when you upload it to another server.
Hi,
I have jsreport running locally - 3.10.0
My test server is also 3.10.0
My deployment method is to export a .zip from my local and then do a "Full" import to the test server.
I have been working on an xlsx file - on my local it will generate like it is supposed to:
But the exact same file, after an import will not work on the test server:
Your help would be appreciated
So it does, thanks for the confirmation