Error in jsreport when update to version 3.1.1



  • Hi sir ,

    When i try to update jsreport version to 3.1.1 in docker file jsreport not l;oading in aws

    My dokerfile,

    ![0_1637760453102_upload-b776666b-ffdf-4e9b-af9f-70b8ebd28f82](Uploading 100%)

    2.Jsreport.config.json

    {
    "allowLocalFilesAccess": true,
    "httpPort": 8084,
    "store": {
    "provider": "fs"
    },
    "extensions": {
    "fs-store": {
    "compactionInterval": 60000,
    "persistence": {
    "provider": "aws-s3"
    },
    "syncModifications": {
    "updateStudio": true
    },
    "sync": {
    "usePolling": true
    }
    },
    "studio": {
    "enabled": true,
    "flushLogsInterval": 60000
    },
    "scheduling": {
    "interval": 60000
    },
    "fs-store-aws-s3-persistence": {
    "accessKeyId": "AKIAR3OLYGOJ6VS5AXEN",
    "secretAccessKey": "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",
    "bucket": "jsreportbucket",
    "lock": {
    "queueName": "jsreport-lock.fifo"
    }
    },
    "scripts": {
    "timeout": 300000,
    "allowedModules": [
    "request",
    ""
    ]
    }
    },
    "phantom": {
    "numberOfWorkers": 2,
    "timeout": 180000,
    "strategy": "dedicated-process"
    },
    "templatingEngines": {
    "numberOfWorkers": 2,
    "timeout": 1800000,
    "strategy": "http-server"
    },
    "tasks": {
    "numberOfWorkers": 2,
    "timeout": 600000,
    "strategy": "dedicated-process",
    "forkOptions": {
    "execArgv": [
    "--max-old-space-size=4096"
    ]
    }
    },
    "scripts": {
    "timeout": 1200000,
    "allowedModules": "
    "
    },
    "express": {
    "renderTimeout": 1800000,
    "inputRequestLimit": "200mb"
    }
    }

    1. Log from AWS

    timestamp,message
    1637758606160,"2021-11-24T12:56:46.159Z - info: Initializing jsreport (version: 3.1.1, configuration file: jsreport.config.json, nodejs: 16.11.0)"
    1637758606162,2021-11-24T12:56:46.161Z - info: Searching for available extensions in /app/
    1637758606164,"2021-11-24T12:56:46.164Z - info: Extensions location cache not found, crawling directories"
    1637758607356,2021-11-24T12:56:47.356Z - info: Found 37 extension(s)
    1637758607373,2021-11-24T12:56:47.372Z - debug: Writing extension locations cache to /tmp/jsreport/core/locations.json
    1637758607374,2021-11-24T12:56:47.374Z - debug: Discovered 37 extensions
    1637758607758,2021-11-24T12:56:47.757Z - info: Using extension authentication@3.0.0
    1637758608173,2021-11-24T12:56:48.173Z - debug: Extension authentication@3.0.0 was disabled
    1637758608174,2021-11-24T12:56:48.174Z - info: Using extension base@3.0.0
    1637758608254,2021-11-24T12:56:48.254Z - info: Using extension child-templates@3.0.0
    1637758608255,2021-11-24T12:56:48.255Z - info: Using extension cli@3.0.0
    1637758608257,2021-11-24T12:56:48.257Z - info: Using extension components@3.0.1
    1637758608258,2021-11-24T12:56:48.258Z - info: Using extension data@3.0.0
    1637758608258,2021-11-24T12:56:48.258Z - info: Using extension express@3.1.0
    1637758608973,2021-11-24T12:56:48.973Z - info: Using extension freeze@3.0.1
    1637758608975,2021-11-24T12:56:48.975Z - info: Using extension fs-store@3.0.0
    1637758609258,2021-11-24T12:56:49.258Z - info: Using extension handlebars@3.0.0
    1637758609259,2021-11-24T12:56:49.259Z - info: Using extension import-export@3.0.1
    1637758609266,2021-11-24T12:56:49.266Z - info: Using extension jsrender@3.0.0
    1637758609267,2021-11-24T12:56:49.267Z - info: Using extension licensing@3.0.1
    1637758609361,2021-11-24T12:56:49.360Z - info: Using extension localization@3.0.1
    1637758609361,2021-11-24T12:56:49.361Z - info: Using extension npm@3.0.1
    1637758609364,2021-11-24T12:56:49.364Z - info: Using extension pdf-utils@3.0.2
    1637758609365,2021-11-24T12:56:49.365Z - info: Using extension reports@3.0.0
    1637758609368,2021-11-24T12:56:49.367Z - info: Using extension tags@3.0.0
    1637758609369,2021-11-24T12:56:49.369Z - info: Using extension text@3.0.0
    1637758609370,2021-11-24T12:56:49.369Z - info: Using extension version-control@3.0.1
    1637758609456,2021-11-24T12:56:49.456Z - info: Using extension assets@3.0.1
    1637758609465,2021-11-24T12:56:49.464Z - info: Using extension authorization@3.0.2
    1637758609470,2021-11-24T12:56:49.468Z - debug: Extension authorization@3.0.2 was disabled
    1637758609470,2021-11-24T12:56:49.469Z - info: Using extension browser-client@3.0.1
    1637758609554,2021-11-24T12:56:49.553Z - info: Using extension chrome-pdf@3.0.0
    1637758609576,"2021-11-24T12:56:49.576Z - debug: Chrome strategy is chrome-pool, numberOfWorkers: 1"
    1637758609577,"2021-11-24T12:56:49.576Z - debug: Chrome custom launch options are executablePath=/usr/lib/chromium/chrome, args=--no-sandbox,--disable-dev-shm-usage"
    1637758609577,2021-11-24T12:56:49.577Z - info: Using extension docx@3.0.1
    1637758609579,2021-11-24T12:56:49.579Z - info: Using extension html-to-xlsx@3.0.1
    1637758609773,2021-11-24T12:56:49.773Z - info: html-to-xlsx detected chrome as available html engine
    1637758609773,2021-11-24T12:56:49.773Z - info: Using extension pptx@3.0.2
    1637758609855,2021-11-24T12:56:49.853Z - info: Using extension scheduling@3.0.1
    1637758609975,2021-11-24T12:56:49.975Z - info: Using extension scripts@3.0.1
    1637758610053,2021-11-24T12:56:50.052Z - info: Using extension static-pdf@3.0.0
    1637758610053,2021-11-24T12:56:50.053Z - info: Using extension studio@3.1.0
    1637758610358,2021-11-24T12:56:50.358Z - info: Using extension xlsx@3.0.1
    1637758610564,2021-11-24T12:56:50.564Z - error: Error occurred during reporter init: Error: Error when loading extension fs-store-aws-s3-persistence@1.4.2
    1637758610564,"Error: Extension ""fs-store-aws-s3-persistence"" is not compatible with ""core"" extension. Missing "".requires"" information in ""fs-store-aws-s3-persistence"" definition"
    1637758610564, at validateMinimalVersion (/app/node_modules/@jsreport/jsreport-core/lib/main/extensions/validateMinimalVersion.js:24:11)
    1637758610564, at Object._useOne (/app/node_modules/@jsreport/jsreport-core/lib/main/extensions/extensionsManager.js:158:9)
    1637758610564, at Object._useMany (/app/node_modules/@jsreport/jsreport-core/lib/main/extensions/extensionsManager.js:99:38)
    1637758610564, at async MainReporter.init (/app/node_modules/@jsreport/jsreport-core/lib/main/reporter.js:199:7)
    1637758610564, at Object._useOne (/app/node_modules/@jsreport/jsreport-core/lib/main/extensions/extensionsManager.js:248:15)
    1637758610564, at Object._useMany (/app/node_modules/@jsreport/jsreport-core/lib/main/extensions/extensionsManager.js:99:38)
    1637758610564, at async MainReporter.init (/app/node_modules/@jsreport/jsreport-core/lib/main/reporter.js:199:7)
    1637758610565,Error: Error when loading extension fs-store-aws-s3-persistence@1.4.2
    1637758610565,"Error: Extension ""fs-store-aws-s3-persistence"" is not compatible with ""core"" extension. Missing "".requires"" information in ""fs-store-aws-s3-persistence"" definition"
    1637758610565, at validateMinimalVersion (/app/node_modules/@jsreport/jsreport-core/lib/main/extensions/validateMinimalVersion.js:24:11)
    1637758610565, at Object._useOne (/app/node_modules/@jsreport/jsreport-core/lib/main/extensions/extensionsManager.js:158:9)
    1637758610565, at Object._useMany (/app/node_modules/@jsreport/jsreport-core/lib/main/extensions/extensionsManager.js:99:38)
    1637758610565, at async MainReporter.init (/app/node_modules/@jsreport/jsreport-core/lib/main/reporter.js:199:7)
    1637758610565, at Object._useOne (/app/node_modules/@jsreport/jsreport-core/lib/main/extensions/extensionsManager.js:248:15)
    1637758610565, at Object._useMany (/app/node_modules/@jsreport/jsreport-core/lib/main/extensions/extensionsManager.js:99:38)
    1637758610565, at async MainReporter.init (/app/node_modules/@jsreport/jsreport-core/lib/main/reporter.js:199:7)



  • In v3, the npm packages are scoped in @jsreport.
    So the fs-store-aws-s3-persistence needs to be installed this way

    npm install @jsreport/jsreport-fs-store-aws-s3-persistence
    

    Docs
    https://jsreport.net/learn/fs-store#aws-s3



  • Is there any other way to write version of jsreport using @latest in docker file.Because every time i have to update docker file when new version comes

    Docker file
    FROM jsreport/jsreport@latest
    USER root

    Is this correct?



  • You always get the image with the latest tag like this:

    FROM jsreport/jsreport
    

    However, I recommend always explicitly setting the version, so you aren't surprised with changes.



  • ok sir



  • const jsreport = require('jsreport-proxy');

    How to install jsreport-proxy using npm ?



  • Also how to install jsreport-fs-store-aws-sns-sync

    1.Logs from aws,

    0_1637774907619_upload-fd8f5fb3-93c0-4afe-b292-e11920188acb

    2.Docker file

    0_1637774798881_upload-e59d10b2-fae9-47f3-86d2-aaeea385503c

    I have added @jsreport but it didnt work



  • const jsreport = require('jsreport-proxy');

    It is a virtual module available in your sandbox. You don't and can't install it.

    jsreport-fs-store-aws-sns-sync

    It isn't needed in the v3 because it implements the sync implicitly through the journal file. In other words, just remove it from your dockerifle.



  • Thank you sir


Log in to reply
 

Looks like your connection to jsreport forum was lost, please wait while we try to reconnect.