Kristian Lange
Kristian Lange
I finally could replicate the issue on an old FF 71.0 on Windows 10. I'll debug now and get back to you.
@alisdt @svoki Can you please try again with the new JATOS version 3.6.1? I did some improvements with with the result data export and in my FF on Windows and...
And do you have an error message now, maybe in the browser's dev tools?
Strange, it's working now on my FF on Windows and Linux. Can you please try something for me: In you _production.conf_ set ``` jatos.resultData.export.useTmpFile = true ``` And restart JATOS...
I might have found the culprit: Is it possible that you disallowed 3rd-party-cookies? It looks like disallowing them also disallows service workers and service workers are needed by a library...
And what happens if you allow third party cookies in your browser (in case you turned them off). Can you then export results again in JATOS? In Cromium it's under:...
I had a look at this StreamSaver.js library that JATOS is using lately to download large files. I wasn't aware that it is downloading two files from a third party...
The error message "Failing because buffer is full ..." indicates that your server has a shortage in some resources, probably memory. Older JATOS version add to this problem in that...
Not sure about the number of open files. Although I never had a problem with those and JATOS. There is no 'verbose' logging in JATOS. Just one logging state. The...
Okay, I will add a property to change the cache size of the exports to the production.conf in the next release. Going back to 3.5.10 won't change the export. The...