noobaa-core icon indicating copy to clipboard operation
noobaa-core copied to clipboard

`npm run pkg` command failed due to an AssertionError

Open Junta-Watanabe opened this issue 1 year ago • 0 comments

Environment info

  • NooBaa Version: noobaa-core-master and guy-p6
  • Platform: stand-alone

Actual behavior

  1. On some machines, the npm run pkg command failed due to an AssertionError as follows:
$ npm run pkg

> [email protected] pkg
> pkg . --public --options unhandled-rejections=warn --compress Brotli

> [email protected]
compression:  Brotli
> Fetching base Node.js binaries to PKG_CACHE_PATH
  fetched-v18.5.0-linux-x64           [                    ] 0%> Not found in remote cache:
  {"tag":"v3.4","name":"node-v18.5.0-linux-x64"}
> Building base binary from source:
  built-v18.5.0-linux-x64
> Fetching Node.js source archive from nodejs.org...
> Error! AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value:

  (0, assert_1.default)(!this.bar)

    at Log.enableProgress (/home/user/setup/noobaa-core/node_modules/pkg-fetch/lib-es5/log.js:64:30)
    at /home/user/setup/noobaa-core/node_modules/pkg-fetch/lib-es5/utils.js:58:31
    at step (/home/user/setup/noobaa-core/node_modules/pkg-fetch/lib-es5/utils.js:33:23)
    at Object.next (/home/user/setup/noobaa-core/node_modules/pkg-fetch/lib-es5/utils.js:14:53)
    at /home/user/setup/noobaa-core/node_modules/pkg-fetch/lib-es5/utils.js:8:71
    at new Promise (<anonymous>)
    at __awaiter (/home/user/setup/noobaa-core/node_modules/pkg-fetch/lib-es5/utils.js:4:12)
    at downloadUrl (/home/user/setup/noobaa-core/node_modules/pkg-fetch/lib-es5/utils.js:53:12)
    at /home/user/setup/noobaa-core/node_modules/pkg-fetch/lib-es5/build.js:142:66
    at step (/home/user/setup/noobaa-core/node_modules/pkg-fetch/lib-es5/build.js:44:23)

Expected behavior

  1. A single-executable package is created.

Steps to reproduce

  1. Issue npm run pkg

More information - Screenshots / Logs / Other output

Sorry for the lack of the detailed information. I haven't found the difference between the machine that could create a single-executable package and that couldn't yet. All the machines are RHEL8.6. If you guys need more information, please let me know, and I'll collect it.

Junta-Watanabe avatar Jun 05 '23 07:06 Junta-Watanabe