Async Header throwing an error when working with Postgress store.

joshplaetzler

Hey Hopefully you can help us out we are trying to switch from using options.reports.async to using jsreport-Options-Reports-Async in the header. And when we run things locally without a DB connection all works well. Once we put it in our labs environment using "@jsreport/jsreport-postgres-store" we get the error bellow. We looked into the odata-to-sql and package but we are a bit stumped as to what would be causing this issue.

(because) cannot read properties of undefined (reading 'forEach')
TypeError: Cannot read properties of undefined (reading 'forEach')
    at module.exports (/app/node_modules/@jsreport/odata-to-sql/lib/query.js:54:28)
    at Object.query (/app/node_modules/@jsreport/odata-to-sql/lib/transformer.js:46:14)
    at Cursor.toArray (/app/node_modules/@jsreport/sql-store/lib/sqlProvider.js:22:29)
    at replay (/app/node_modules/@jsreport/jsreport-core/lib/main/store/collection.js:53:21)
    at /app/node_modules/@jsreport/jsreport-core/lib/main/store/collection.js:60:18
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Object.findOne (/app/node_modules/@jsreport/jsreport-core/lib/main/store/collection.js:93:17)
    at async findEntity (/app/node_modules/@jsreport/jsreport-core/lib/main/store/setupValidateShortid.js:63:26)
    at async validateShortid (/app/node_modules/@jsreport/jsreport-core/lib/main/store/setupValidateShortid.js:45:26)
    at async ListenerCollection.fire (/app/node_modules/@jsreport/jsreport-core/lib/shared/listenerCollection.js:157:21)

admin

Hi, it seems to work for me fine...

Are you on the latest 4.8.0? There was a fix included for the jsreport-Options-Reports-Async.
Is there anything specific you do? Authentication enabled, some extra configs... ?

joshplaetzler

We are currently on 4.7.0 we will try upgrading to 4.8.0 and see if that fixes the issue and let you know.
No Authentication enabled.

joshplaetzler

Thanks, upgrading to 4.8.0 fixes that issue.

However, now we are seeing an issue where if we set our workers to 1 it doesn't queue up after the first request everything just runs. Where before we used the header it would queue up but not respond with the location id until a worker was available.