JSReports stuck on spinning wheel

Evan Furbeyre

Our deployment of JSReport has stopped working. Reverting to previously working commits has not fixed anything. Checking the browser console shows these errors.

client.995b9a360c73213831bd.js:1 TypeError: Cannot read property 'object' of undefined
at Object.<anonymous> (studio-extensions.client.ad226f628cd42cdbbd0a.js:17377)
at webpack_require (studio-extensions.client.ad226f628cd42cdbbd0a.js:16814)
at Object.<anonymous> (studio-extensions.client.ad226f628cd42cdbbd0a.js:17458)
at webpack_require (studio-extensions.client.ad226f628cd42cdbbd0a.js:16814)
at studio-extensions.client.ad226f628cd42cdbbd0a.js:16878
at Object.1575 (studio-extensions.client.ad226f628cd42cdbbd0a.js:16881)
at i (client.995b9a360c73213831bd.js:1)
at client.995b9a360c73213831bd.js:66
i.oe @ client.995b9a360c73213831bd.js:1
studio-extensions.client.ad226f628cd42cdbbd0a.js:17377 Uncaught (in promise) TypeError: Cannot read property 'object' of undefined
at Object.<anonymous> (studio-extensions.client.ad226f628cd42cdbbd0a.js:17377)
at webpack_require (studio-extensions.client.ad226f628cd42cdbbd0a.js:16814)
at Object.<anonymous> (studio-extensions.client.ad226f628cd42cdbbd0a.js:17458)
at webpack_require (studio-extensions.client.ad226f628cd42cdbbd0a.js:16814)
at studio-extensions.client.ad226f628cd42cdbbd0a.js:16878
at Object.1575 (studio-extensions.client.ad226f628cd42cdbbd0a.js:16881)
at i (client.995b9a360c73213831bd.js:1)
at client.995b9a360c73213831bd.js:66

This is our Dockerfile:

FROM jsreport/jsreport:2.6.1-full

RUN npm install \
        jsreport/jsreport-scheduling \
	dotenv \
	moment \
	nodemailer \
	numeral \
	pg 
WORKDIR /app
COPY jsreport.config.json ./

COPY data ./data/

jan_blaha

Hi,

you use git dependency for jsreport/jsreport-scheduling extension in your dockerfile.
The git mater version has likely some changes that won't work with your current version of jsreport 2.6.1.
Try to remove the jsreport/jsreport-scheduling install from your dockerfile.

Evan Furbeyre

Ok I am trying that, but it seems that long overdue schedules are now being sent.

Is the following block supposed to prevent schedules that are more than 5 minutes overdue from sending? Or is there a different configuration now?

{
    "extensions": {
        "scheduling": {
            "misfireThreshold": 300000
        },
    }
}

jan_blaha

I see, please install jsreport-scheduling version 2.2.0. There is this config available and it should still work with your jsreport version

RUN npm install jsreport-scheduling@2.2.0

https://github.com/jsreport/jsreport-scheduling/releases

Evan Furbeyre

Currently getting the following error:

Could not install from "jsreport/jsreport-scheduling@2.2.0" as it does not contain a package.json file.

jan_blaha

It shouldn't be jsreport/jsreport-scheduling@2.2.0.

Correct is:

RUN npm install jsreport-scheduling@2.2.0

Evan Furbeyre

That worked great. Thank you!