Flood fails to start after todays rebuild

[mirolm]

Type: Bug Report

• Try to follow the update procedure described in the README and try again before opening this issue.
• Please check the F.A.Q..
• Please check the Troubleshooting wiki section.

Your Environment

• Version used:
  • Version (stable release) git --no-pager tag v3.1.0
  • Commit ID (development release) git --no-pager log -1 commit f1f0b3c (HEAD -> master, origin/master, origin/HEAD)
• Environment name and version:
  • Node.js version node --version v14.14.0
  • npm version npm --version 6.14.8
  • Web browser name and version Chromium Version 86.0.4240.111 (Official Build) Arch Linux (64-bit)
• Operating System and version: Debian Buster x64

Summary

After last time i rebuild flood it failed to start. Error messages can be seen below:

flood_start.txt
2020-10-21T16_39_22_182Z-debug.log

Expected Behavior

Flood should start normally.

Current Behavior

Flood fails to start.

Possible Solution

None.

Steps to Reproduce

1. git checkout .
2. git pull
3. npm install
4. npm run build
5. npm prune --production
6. npm start
7. ...

Context

None.

[jesec]

Can't reproduce.

Build log (f1f0b3c)

 [~/flood] [G master f1f0b3c] [package-lock.json: regenerate]
 Θ git clean -ffdx
Removing node_modules/

 [~/flood] [G master f1f0b3c] [package-lock.json: regenerate]
 Θ npm install

> node-sass@4.14.1 install /home/jc/flood/node_modules/node-sass
> node scripts/install.js

Cached binary found at /home/jc/.npm/node-sass/4.14.1/linux-x64-83_binding.node

> core-js-pure@3.6.5 postinstall /home/jc/flood/node_modules/core-js-pure
> node -e "try{require('./postinstall')}catch(e){}"

Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!

The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
> https://opencollective.com/core-js
> https://www.patreon.com/zloirock

Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)


> node-sass@4.14.1 postinstall /home/jc/flood/node_modules/node-sass
> node scripts/build.js

Binary found at /home/jc/flood/node_modules/node-sass/vendor/linux-x64-83/binding.node
Testing binary
Binary is fine
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/webpack-dev-server/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/watchpack-chokidar2/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.3 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

added 2274 packages from 1240 contributors and audited 2288 packages in 25.045s

100 packages are looking for funding
  run `npm fund` for details

found 2 low severity vulnerabilities
  run `npm audit fix` to fix them, or `npm audit` for details

 [~/flood] [G master f1f0b3c] [package-lock.json: regenerate]
 Θ npm run build

> flood@3.1.0 build /home/jc/flood
> npm run build-assets && npm run build-ts


> flood@3.1.0 build-assets /home/jc/flood
> node client/scripts/build.js

Creating an optimized production build...

✔ Webpack
  Compiled successfully in 17.98s

Compiled successfully.

File sizes after gzip:

  105.81 KB  assets/static/js/main.4668282f.js
  36.49 KB   assets/static/js/18.10a23f14.chunk.js
  28.17 KB   assets/static/js/22.ce7d3580.chunk.js
  24.87 KB   assets/static/js/21.ec73449c.chunk.js
  24.07 KB   assets/static/js/23.485bba42.chunk.js
  15.61 KB   assets/static/css/main.25877d8cb8d46f8def11.css
  7.8 KB     assets/static/js/0.2997c1e1.chunk.js
  7.46 KB    assets/static/js/4.c2cbf443.chunk.js
  6.63 KB    assets/static/js/5.df127372.chunk.js
  6.1 KB     assets/static/js/2.25a049ee.chunk.js
  6.07 KB    assets/static/js/7.2d5c8771.chunk.js
  5.98 KB    assets/static/js/48.bc43c2ee.chunk.js
  5.81 KB    assets/static/js/44.91ee6b64.chunk.js
  5.47 KB    assets/static/js/13.ab877522.chunk.js
  5.44 KB    assets/static/js/10.a6a77c8c.chunk.js
  5.42 KB    assets/static/js/25.99d4e382.chunk.js
  5.38 KB    assets/static/js/37.bbb27d85.chunk.js
  5.38 KB    assets/static/js/12.b611509e.chunk.js
  5.32 KB    assets/static/js/15.d60c677e.chunk.js
  5.31 KB    assets/static/js/35.47bbf8da.chunk.js
  5.29 KB    assets/static/js/27.786b3230.chunk.js
  5.23 KB    assets/static/js/41.70f6be41.chunk.js
  5.23 KB    assets/static/js/38.a57a94ce.chunk.js
  5.16 KB    assets/static/js/43.7d493d54.chunk.js
  5.13 KB    assets/static/js/33.c07f38fc.chunk.js
  5.07 KB    assets/static/js/42.2389f8ae.chunk.js
  5.06 KB    assets/static/js/51.ab7ce3f6.chunk.js
  5.03 KB    assets/static/js/29.4f15ef52.chunk.js
  5.02 KB    assets/static/js/40.98b7db3c.chunk.js
  5.01 KB    assets/static/js/11.1f56a5f1.chunk.js
  5 KB       assets/static/js/31.dffe1162.chunk.js
  5 KB       assets/static/js/46.c9d7122e.chunk.js
  4.97 KB    assets/static/js/39.77dc2791.chunk.js
  4.95 KB    assets/static/js/36.d5c9330f.chunk.js
  4.92 KB    assets/static/js/50.70d41708.chunk.js
  4.92 KB    assets/static/js/6.48d56f68.chunk.js
  4.88 KB    assets/static/js/3.70a188b9.chunk.js
  4.8 KB     assets/static/js/1.da8e0514.chunk.js
  4.8 KB     assets/static/js/8.1168c1f5.chunk.js
  4.75 KB    assets/static/js/16.0bbbc0c9.chunk.js
  4.64 KB    assets/static/js/14.fc89f2b2.chunk.js
  4.49 KB    assets/static/js/24.6ba9f730.chunk.js
  4.49 KB    assets/static/js/26.2a88498c.chunk.js
  4.49 KB    assets/static/js/28.0a67fc0f.chunk.js
  4.49 KB    assets/static/js/32.4002326b.chunk.js
  4.49 KB    assets/static/js/34.5df6dde8.chunk.js
  4.49 KB    assets/static/js/45.d2ef0260.chunk.js
  4.49 KB    assets/static/js/49.627e197b.chunk.js
  4.49 KB    assets/static/js/30.f6ec877a.chunk.js
  4.49 KB    assets/static/js/47.51b65f26.chunk.js
  4.33 KB    assets/static/js/19.7ad12add.chunk.js
  4.22 KB    assets/static/js/9.9c0e5d21.chunk.js
  3.26 KB    assets/static/js/17.ad4d3735.chunk.js

> flood@3.1.0 build-ts /home/jc/flood
> ncc build server/bin/start.ts -m -t -e argon2-browser -e geoip-country

ncc: Version 0.24.1
ncc: Compiling file index.js
ncc: Using typescript@4.0.3 (local user-provided)
1872kB  dist/index.js
1872kB  [22476ms] - ncc 0.24.1

 [~/flood] [G master f1f0b3c] [package-lock.json: regenerate]
 Θ npm prune --production
removed 2242 packages and audited 34 packages in 12.883s

1 package is looking for funding
  run `npm fund` for details

found 0 vulnerabilities


 [~/flood] [G master f1f0b3c] [package-lock.json: regenerate]
 Θ npm start

> flood@3.1.0 start /home/jc/flood
> node --use_strict dist/index.js

Flood server starting on http://127.0.0.1:3000.

[jesec]

It might be related to package-lock.json regeneration. Use npm ci or remove node_modules to ensure caches are removed.

[mirolm]

This is strange... now it managed to run without issues.

I have done several times clean clone of the repo and got the errors. Then i started to checkout commit by commit to try to catch where it breaks. Got to the last commit and it runs fine.

Now even clean clone of the repo works fine.