EMBER_CLI_PROD_ASSETS para 1 falha na pré-compilação de assets

Suporte ao Produto
12

Apenas para constar, e se for útil para alguém. Existe pelo menos uma maneira de fazer o ember cli funcionar como esperado com um uid aleatório, e isso é garantir que o uid aleatório atribuído tenha uma entrada em /etc/passwd no momento de executar a operação rake assets:precompile.

Algo como:

if [ `id -u` -ge 10000 ]; then
  cat /etc/passwd | sed -e "s/^discourse:/builder:/" > /tmp/passwd
  echo "discourse:x:`id -u`:`id -g`:,,,:/home/discourse:/bin/bash" >> /tmp/passwd
  cat /tmp/passwd > /etc/passwd
  rm /tmp/passwd
fi

Assim, o comando app/assets/javascripts/discourse run ember build -prod (de discourse/assets.rake at tests-passed · discourse/discourse · GitHub) funcionará.

yarn run v1.22.17
$ /discourse/app/assets/javascripts/node_modules/.bin/ember build -prod
WARNING: Node v16.13.2 is not tested against Ember CLI on your platform. We recommend that you use the most-recent "Active LTS" version of Node.js. See https://git.io/v7S5n  for details.
DEPRECATION: The integration of jQuery into Ember has been deprecated and will be removed with Ember 4.0. You can either opt-out of using jQuery, or install the `@ember/jquery` addon to provide the jQuery integration. Please consult the deprecation guide for further details: https://emberjs.com/deprecations/v3.x#toc_jquery-apis 
- Building
Environment: production
- Building
- building... 
[WARN] (broccoli-terser-sourcemap) Minifying "assets/chunk.529.6ee9018498e97f872147.js" took: 24288ms (more than 20,000ms)
...

Também notei que essa operação é bastante custosa, consumindo quase 2GB de RAM apenas para pré-compilar :scream:

Abraços,
Ismael