Error en la sintaxis de Ruby 3.2 en instalación estándar

Tuve el mismo error que este mensaje en una instalación estándar durante una actualización desde el navegador. El error ocurrió durante las operaciones plugin:pull_compatible_all y multisite:migrate, no durante la precompilación de activos.

El error:

SyntaxError: /var/www/discourse/lib/file_store/base_store.rb:96: syntax error, unexpected ','
      download(*, **, print_deprecation: false)

El registro completo de la actualización copiado desde la interfaz del navegador:

********************************************************
*** Por favor, ten paciencia, los siguientes pasos pueden tardar un rato ***
********************************************************
Ciclando Unicorn para liberar memoria
Reiniciando unicorn pid: 559
Esperando a que Unicorn se recargue.
Esperando a que Unicorn se recargue..
Esperando a que Unicorn se recargue...
Esperando a que Unicorn se recargue....
Esperando a que Unicorn se recargue.....
Esperando a que Unicorn se recargue......
Esperando a que Unicorn se recargue.......
Esperando a que Unicorn se recargue........
Deteniendo 1 trabajador(es) de Unicorn para liberar memoria
Deteniendo la cola de trabajos para recuperar memoria, el pid del maestro es 15009
$ cd /var/www/discourse && git fetch --tags --force && git reset --hard HEAD@{upstream}
Usando openssl-signature_algorithm 1.2.1
Usando aws-sigv4 1.5.0
Usando faraday 2.7.2
Usando image_optim 0.31.2
Usando request_store 1.5.1
Usando logstash-logger 0.26.1
Usando message_bus 4.3.1
Usando mini_racer 0.6.3
Usando sidekiq 6.5.8
Usando mini_suffix 0.3.3
Usando oauth-tty 1.0.5
Usando snaky_hash 2.0.1
Usando omniauth 1.9.2
Usando pry 0.14.2
Usando puma 6.0.2
Usando rack-mini-profiler 3.0.0
Usando rack-protection 3.0.5
Usando rbtrace 0.4.14
Usando redis-namespace 1.9.0
Usando rqrcode 2.1.2
Usando rss 0.2.9
Usando sassc 2.0.1
Usando sprockets 3.7.2
Usando uglifier 4.2.0
Usando unf 0.1.4
Usando unicorn 6.1.0
Usando web-push 3.0.0
Usando loofah 2.19.1
Usando net-imap 0.3.1
Usando net-pop 0.1.2
Usando net-smtp 0.3.3
Usando cose 1.3.0
Usando css_parser 1.13.0
Usando ruby-readability 0.7.0
Usando sanitize 6.0.0
Usando ecma-re-validator 0.4.0
Usando activesupport 7.0.4.3
Usando rails-html-sanitizer 1.5.0
Usando globalid 1.0.1
Usando activemodel 7.0.4.3
Usando aws-sdk-core 3.130.2
Usando faraday-retry 2.0.0
Usando json_schemer 0.2.23
Usando mini_scheduler 0.15.0
Usando oauth 1.1.0
Usando oauth2 1.4.11
Usando pry-byebug 3.10.1
Usando pry-rails 0.3.9
Usando rails-dom-testing 2.0.3
Usando actionview 7.0.4.3
Usando activejob 7.0.4.3
Usando active_model_serializers 0.8.4
Usando activerecord 7.0.4.3
Usando aws-sdk-kms 1.56.0
Usando aws-sdk-sns 1.53.0
Usando omniauth-oauth2 1.7.3
Usando omniauth-oauth 1.2.0
Usando actionpack 7.0.4.3
Usando actionview_precompiler 0.2.3
Usando aws-sdk-s3 1.114.0
Usando discourse-seed-fu 2.3.12
Usando omniauth-facebook 9.0.0
Usando omniauth-github 1.4.0
Usando omniauth-google-oauth2 0.8.2
Usando omniauth-twitter 1.4.0
Usando railties 7.0.4.3
Usando sprockets-rails 3.4.2
Usando mail 2.8.0.edge desde https://github.com/discourse/mail.git (en main@5b700fc)
Usando lograge 0.12.0
Usando rails_failover 0.8.1
Usando rails_multisite 4.0.1
Usando sassc-rails 2.1.2
Usando actionmailer 7.0.4.3
Instalando uri 0.12.2
Usando net-http 0.3.2
¡Bundling completo! 135 dependencias del Gemfile, 171 gemas ahora instaladas.
Las gemas en los grupos «test» y «development» no se instalaron.
Las gemas empaquetadas se instalan en `./vendor/bundle`
$ yarn install --production
yarn install v1.22.19
[1/5] Validando package.json...
[2/5] Resolviendo paquetes...
success Ya está actualizado.
$ yarn --cwd app/assets/javascripts/discourse $(node -e 'if(JSON.parse(process.env.npm_config_argv).original.includes(`--frozen-lockfile`)){console.log(`--frozen-lockfile`)}')
yarn install v1.22.19
[1/4] Resolviendo paquetes...
[2/4] Obteniendo paquetes...
[3/4] Enlazando dependencias...
[4/4] Construyendo paquetes frescos...
success Archivo de bloqueo guardado.
Hecho en 8.84s.
Hecho en 9.31s.
$ LOAD_PLUGINS=0 bundle exec rake plugin:pull_compatible_all
rake aborted!
SyntaxError: /var/www/discourse/lib/file_store/base_store.rb:96: syntax error, unexpected ','
      download(*, **, print_deprecation: false)
                ^
/var/www/discourse/lib/file_store/base_store.rb:102: syntax error, unexpected ','
      download(*, **, print_deprecation: false)
                ^
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/bootsnap-1.15.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/bootsnap-1.15.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/zeitwerk-2.6.6/lib/zeitwerk/kernel.rb:38:in `require'
/var/www/discourse/lib/file_store/local_store.rb:3:in `<main>'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/bootsnap-1.15.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/bootsnap-1.15.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/zeitwerk-2.6.6/lib/zeitwerk/kernel.rb:38:in `require'
/var/www/discourse/lib/tasks/posts.rake:3:in `<main>'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/railties-7.0.4.3/lib/rails/engine.rb:661:in `load'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/railties-7.0.4.3/lib/rails/engine.rb:661:in `block in run_tasks_blocks'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/railties-7.0.4.3/lib/rails/engine.rb:661:in `each'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/railties-7.0.4.3/lib/rails/engine.rb:661:in `run_tasks_blocks'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/railties-7.0.4.3/lib/rails/application.rb:506:in `run_tasks_blocks'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/railties-7.0.4.3/lib/rails/engine.rb:464:in `load_tasks'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/railties-7.0.4.3/lib/rails/railtie.rb:226:in `public_send'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/railties-7.0.4.3/lib/rails/railtie.rb:226:in `method_missing'
/var/www/discourse/Rakefile:9:in `<top (required)>'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/rake-13.0.6/exe/rake:27:in `<top (required)>'
/var/www/discourse/vendor/bundle/ruby/3.1.0/bin/bundle:25:in `load'
/var/www/discourse/vendor/bundle/ruby/3.1.0/bin/bundle:25:in `<main>'
(Ve el rastreo completo ejecutando la tarea con --trace)
No se pudieron verificar las versiones compatibles de los plugins
$ SKIP_POST_DEPLOYMENT_MIGRATIONS=1 bundle exec rake multisite:migrate
rake aborted!
SyntaxError: /var/www/discourse/lib/file_store/base_store.rb:96: syntax error, unexpected ','
      download(*, **, print_deprecation: false)
                ^
/var/www/discourse/lib/file_store/base_store.rb:102: syntax error, unexpected ','
      download(*, **, print_deprecation: false)
                ^
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/bootsnap-1.15.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/bootsnap-1.15.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/zeitwerk-2.6.6/lib/zeitwerk/kernel.rb:38:in `require'
/var/www/discourse/lib/file_store/local_store.rb:3:in `<main>'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/bootsnap-1.15.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/bootsnap-1.15.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/zeitwerk-2.6.6/lib/zeitwerk/kernel.rb:38:in `require'
/var/www/discourse/lib/tasks/posts.rake:3:in `<main>'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/railties-7.0.4.3/lib/rails/engine.rb:661:in `load'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/railties-7.0.4.3/lib/rails/engine.rb:661:in `block in run_tasks_blocks'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/railties-7.0.4.3/lib/rails/engine.rb:661:in `each'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/railties-7.0.4.3/lib/rails/engine.rb:661:in `run_tasks_blocks'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/railties-7.0.4.3/lib/rails/application.rb:506:in `run_tasks_blocks'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/railties-7.0.4.3/lib/rails/engine.rb:464:in `load_tasks'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/railties-7.0.4.3/lib/rails/railtie.rb:226:in `public_send'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/railties-7.0.4.3/lib/rails/railtie.rb:226:in `method_missing'
/var/www/discourse/Rakefile:9:in `<top (required)>'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/rake-13.0.6/exe/rake:27:in `<top (required)>'
/var/www/discourse/vendor/bundle/ruby/3.1.0/bin/bundle:25:in `load'
/var/www/discourse/vendor/bundle/ruby/3.1.0/bin/bundle:25:in `<main>'
(Ve el rastreo completo ejecutando la tarea con --trace)
Docker Manager: FALLÓ LA ACTUALIZACIÓN
#<RuntimeError: RuntimeError>
/var/www/discourse/plugins/docker_manager/lib/docker_manager/upgrader.rb:209:in `run'
/var/www/discourse/plugins/docker_manager/lib/docker_manager/upgrader.rb:101:in `upgrade'
/var/www/discourse/plugins/docker_manager/scripts/docker_manager_upgrade.rb:19:in `block in <main>'
/var/www/discourse/plugins/docker_manager/scripts/docker_manager_upgrade.rb:6:in `fork'
/var/www/discourse/plugins/docker_manager/scripts/docker_manager_upgrade.rb:6:in `<main>'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/railties-7.0.4.3/lib/rails/commands/runner/runner_command.rb:43:in `load'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/railties-7.0.4.3/lib/rails/commands/runner/runner_command.rb:43:in `perform'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/thor-1.2.1/lib/thor/command.rb:27:in `run'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/thor-1.2.1/lib/thor/invocation.rb:127:in `invoke_command'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/thor-1.2.1/lib/thor.rb:392:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/railties-7.0.4.3/lib/rails/command/base.rb:87:in `perform'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/railties-7.0.4.3/lib/rails/command.rb:48:in `invoke'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/railties-7.0.4.3/lib/rails/commands.rb:18:in `<main>'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/bootsnap-1.15.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/bootsnap-1.15.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require'
bin/rails:18:in `<main>'
Levantando 1 trabajador(es) de Unicorn que se detuvieron inicialmente

Ejecutar la actualización desde la consola (git pull && ./launcher rebuild app, como se menciona aquí) provocó otro error, pero no estoy seguro de cuál es el mensaje de error relevante aquí:

I, [2023-07-04T08:08:49.261121 #1]  INFO -- : > cd /var/www/discourse && su discourse -c 'bundle exec rake themes:update assets:precompile'
- Construyendo
- Construyendo
- construyendo...
- limpiando
- limpiando
Error de compilación (broccoli-persistent-filter:Babel > [Babel: @ember/test-helpers]) en @ember/test-helpers/-internal/build-registry.js

[BABEL]: --- PAQUETE MARCADOR ---
Esta versión de @babel/plugin-proposal-private-property-in-object no está destinada a ser importada. Algo está importando
@babel/plugin-proposal-private-property-in-object sin declararlo en sus
dependencias (o devDependencies) en el archivo package.json.
Agrega "@babel/plugin-proposal-private-property-in-object" a tus devDependencies
para solucionar este error. Esto hará que este mensaje desaparezca.
 (Mientras se procesa: /var/www/discourse/app/assets/javascripts/node_modules/@babel/preset-env/lib/index.js)Error: [BABEL]: --- PAQUETE MARCADOR ---
Esta versión de @babel/plugin-proposal-private-property-in-object no está destinada a ser importada. Algo está importando
@babel/plugin-proposal-private-property-in-object sin declararlo en sus
dependencias (o devDependencies) en el archivo package.json.
Agrega "@babel/plugin-proposal-private-property-in-object" a tus devDependencies
para solucionar este error. Esto hará que este mensaje desaparezca.
 (Mientras se procesa: /var/www/discourse/app/assets/javascripts/node_modules/@babel/preset-env/lib/index.js)
    at Object.<anonymous> (/var/www/discourse/app/assets/javascripts/node_modules/@babel/preset-env/node_modules/@babel/plugin-proposal-private-property-in-object/lib/index.js:28:7)
    at Module._compile (node:internal/modules/cjs/loader:1256:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
    at Module.load (node:internal/modules/cjs/loader:1119:32)
    at Module._load (node:internal/modules/cjs/loader:960:12)
    at Module.require (node:internal/modules/cjs/loader:1143:19)
    at require (node:internal/modules/cjs/helpers:110:18)
    at Object.<anonymous> (/var/www/discourse/app/assets/javascripts/node_modules/@babel/preset-env/lib/available-plugins.js:62:46)
    at Module._compile (node:internal/modules/cjs/loader:1256:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
    at Module.load (node:internal/modules/cjs/loader:1119:32)
    at Module._load (node:internal/modules/cjs/loader:960:12)
    at Module.require (node:internal/modules/cjs/loader:1143:19)
    at require (node:internal/modules/cjs/helpers:110:18)
    at Object.<anonymous> (/var/www/discourse/app/assets/javascripts/node_modules/@babel/preset-env/lib/filter-items.js:11:25)
    at Module._compile (node:internal/modules/cjs/loader:1256:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
    at Module.load (node:internal/modules/cjs/loader:1119:32)
    at Module._load (node:internal/modules/cjs/loader:960:12)
    at Module.require (node:internal/modules/cjs/loader:1143:19)
    at require (node:internal/modules/cjs/helpers:110:18)
    at Object.<anonymous> (/var/www/discourse/app/assets/javascripts/node_modules/@babel/preset-env/lib/index.js:16:20)
    at Module._compile (node:internal/modules/cjs/loader:1256:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
    at Module.load (node:internal/modules/cjs/loader:1119:32)
    at Module._load (node:internal/modules/cjs/loader:960:12)
    at Module.require (node:internal/modules/cjs/loader:1143:19)
    at require (node:internal/modules/cjs/helpers:110:18)


Rastreo de pila e informe de error: /tmp/error.dump.5abe6326cd5a415063a7ad1c85649486.log
error El comando falló con código de salida 1.
I, [2023-07-04T08:09:05.088181 #1]  INFO -- : Verificando «Video Upload» para «default»... actualizado
yarn run v1.22.19
$ /var/www/discourse/app/assets/javascripts/node_modules/.bin/ember build -prod
ADVERTENCIA: Node v18.16.1 no se ha probado contra Ember CLI en tu plataforma. Recomendamos que uses la versión más reciente de «Active LTS» de Node.js. Consulta https://git.io/v7S5n para más detalles.
Entorno: producción
limpiando...
Para más información, visita https://yarnpkg.com/en/docs/cli/run

I, [2023-07-04T08:09:05.089002 #1]  INFO -- : Terminando procesos asíncronos
I, [2023-07-04T08:09:05.089274 #1]  INFO -- : Enviando INT a HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/13/bin/postmaster -D /etc/postgresql/13/main pid: 42
103:signal-handler (1688458145) Recibido SIGTERM, programando apagado...
I, [2023-07-04T08:09:05.089522 #1]  INFO -- : Enviando TERM a exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 103
2023-07-04 08:09:05.089 UTC [42] LOG:  recibido solicitud de apagado rápido
103:M 04 Jul 2023 08:09:05.183 # Usuario solicitó apagado...
103:M 04 Jul 2023 08:09:05.183 * Guardando la instantánea RDB final antes de salir.
2023-07-04 08:09:05.186 UTC [42] LOG:  abortando cualquier transacción activa
2023-07-04 08:09:05.190 UTC [42] LOG:  trabajador en segundo plano «lanzador de replicación lógica» (PID 51) salió con código 1
2023-07-04 08:09:05.190 UTC [46] LOG:  apagando
103:M 04 Jul 2023 08:09:05.388 * DB guardado en disco
103:M 04 Jul 2023 08:09:05.389 # Redis está listo para salir, adiós...
2023-07-04 08:09:05.431 UTC [42] LOG:  el sistema de base de datos se ha apagado


FALLÓ
--------------------
Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle exec rake themes:update assets:precompile' falló con retorno #<Process::Status: pid 2323 exit 1>
Ubicación del fallo: /usr/local/lib/ruby/gems/3.2.0/gems/pups-1.1.1/lib/pups/exec_command.rb:117:in `spawn'
exec falló con los parámetros {"cd"=>"$home", "hook"=>"assets_precompile", "cmd"=>["su discourse -c 'bundle exec rake themes:update assets:precompile'"]}
el arranque falló con código de salida 1
** EL ARRANQUE FALLÓ ** por favor, desplázate hacia arriba y busca mensajes de error anteriores, puede haber más de uno.
./discourse-doctor puede ayudar a diagnosticar el problema.
f1dc57af807a68bb877ce724ea4a3424c77d39250b8ee20cb022194938925ce8

Revertí al commit que tenía antes del git pull (cdc5f905a2f245171b9f53fb76f4ba947389fc6b) y reconstruí de nuevo, obteniendo el mismo error.

Probé ./discourse-doctor y falló con el mismo error de babel. Indicó que la instalación usa plugins no oficiales y sugirió desactivarlos, pero ¿cómo puedo hacer eso sin una aplicación funcional? Todos los plugins se instalaron desde la interfaz del navegador, no en app.yaml.

Cuando reinicio la aplicación obtengo un «Oops - Error 500» en el navegador. Al entrar en la aplicación, /var/www/discourse/log/production.log muestra el mismo error de sintaxis, y la versión de ruby es efectivamente 3.1 (ruby 3.1.3p185 (2022-11-24 revision 1a6b16756e) [x86_64-linux]).

El foro está roto ahora. ¿Cómo puedo arreglar la versión de ruby? ¿O la reconstrucción? ¿O revertir a una aplicación funcional?

Mi app.yml con los comentarios eliminados y los identificadores censurados:

templates:
  - "templates/postgres.template.yml"
  - "templates/redis.template.yml"
  - "templates/web.template.yml"
  - "templates/web.ssl.template.yml"
  - "templates/web.letsencrypt.ssl.template.yml"
  - "templates/sshd.template.yml"
  - "templates/web.ratelimited.template.yml"

expose:
  - "80:80"
  - "443:443"
  - "2222:22"

params:
  db_default_text_search_config: "pg_catalog.english"
  db_shared_buffers: "128MB"
  version: stable

env:
  LANG: en_US.UTF-8
  UNICORN_WORKERS: 2
  DISCOURSE_DEVELOPER_EMAILS: 'redacted'
  DISCOURSE_HOSTNAME: 'redacted'
  DISCOURSE_SMTP_ADDRESS: "redacted"
  DISCOURSE_SMTP_PORT: 25
  DISCOURSE_SMTP_USER_NAME: "redacted"
  DISCOURSE_SMTP_PASSWORD: "redacted"
  DISCOURSE_SMTP_ENABLE_START_TLS: true
  LETSENCRYPT_ACCOUNT_EMAIL: "redacted"
  DISCOURSE_MAXMIND_LICENSE_KEY: "redacted"
  DISCOURSE_REFRESH_MAXMIND_DB_DURING_PRECOMPILE_DAYS: 0

volumes:
  - volume:
      host: /var/discourse/shared/standalone
      guest: /shared
  - volume:
      host: /var/discourse/shared/standalone/log/var-log
      guest: /var/log

hooks:
  after_code:
    - exec:
        cd: $home/plugins
        cmd:
          - mkdir -p plugins
          - git clone https://github.com/discourse/docker_manager.git

run:
  - exec: echo «Inicio de comandos personalizados»

  - exec: echo «Fin de comandos personalizados»
  - exec: awk -F\# '{print $1;}' ~/.ssh/authorized_keys | awk 'BEGIN { print «Claves SSH autorizadas para este contenedor:"; } NF>=2 {print $NF;}'
1 me gusta

Es feriado en los EE. UU., así que no es un buen momento para tener un problema… ¿podrías compartir la salida de discourse-doctor?

Sospecho que tal vez docker-manager no se ha actualizado, pero es igualmente probable que necesites deshabilitar tus plugins. Desafortunadamente, no sé cómo lo harías, ya que tu app.yml no parece contener nada más que docker_manager.

1 me gusta

Quizás sea un error en tu tema.

¿./launcher start app?

¿Pondrá tu sitio en marcha?

1 me gusta

Mientras tanto, modifiqué /var/www/discourse/lib/file_store/base_store.rb directamente dentro del contenedor para que sea compatible con Ruby 3.1 (cambié * por *args y ** por **kwargs), reinicié la aplicación y ahora el foro parece funcionar.

Revisé los plugins y en realidad solo hay uno habilitado: docker_manager en la versión 0.1. Hay dos más que están deshabilitados (chat y styleguide).

Aquí está el registro del doctor:

DISCOURSE DOCTOR Tue Jul 4 08:34:54 UTC 2023
OS: Linux redacted 4.9.0-19-amd64 #1 SMP Debian 4.9.320-2 (2022-06-30) x86_64 GNU/Linux


Found containers/app.yml

==================== YML SETTINGS ====================
DISCOURSE_HOSTNAME=redacted
SMTP_ADDRESS="redacted" # (obligatorio)
DEVELOPER_EMAILS=redacted
SMTP_PASSWORD="redacted" # (opcional)
SMTP_PORT=25 # (opcional)
SMTP_USER_NAME="redacted" # (opcional)
LETSENCRYPT_ACCOUNT_EMAIL=redacted

==================== DOCKER INFO ====================
DOCKER VERSION: Docker version 19.03.15, build 99e3ed8919

DOCKER PROCESSES (docker ps -a)

CONTAINER ID        IMAGE                 COMMAND             CREATED             STATUS                      PORTS               NAMES
91601890406d        local_discourse/app   "/sbin/boot"        4 months ago        Exited (5) 17 minutes ago                       app

==================== SERIOUS PROBLEM!!!! ====================
app not running!
Attempting to rebuild
==================== REBUILD LOG ====================
x86_64 arch detected.
Ensuring launcher is up to date
Fetching origin
Launcher is up-to-date
Stopping old container
+ /usr/bin/docker stop -t 600 app
app
2.0.20230703-0055: Pulling from discourse/base
Digest: sha256:a943db5c56ee8b2025ec550b42fe12ecfa63990d428f43ba8358ca3632b5335f
Status: Image is up to date for discourse/base:2.0.20230703-0055
docker.io/discourse/base:2.0.20230703-0055
/usr/local/lib/ruby/gems/3.2.0/gems/pups-1.1.1/lib/pups.rb
/usr/local/bin/pups --stdin
I, [2023-07-04T08:35:07.717173 #1]  INFO -- : Reading from stdin
I, [2023-07-04T08:35:07.722553 #1]  INFO -- : > locale-gen $LANG && update-locale
I, [2023-07-04T08:35:07.786023 #1]  INFO -- : Generating locales (this might take a while)...
Generation complete.

I, [2023-07-04T08:35:07.786357 #1]  INFO -- : > mkdir -p /shared/postgres_run
I, [2023-07-04T08:35:07.789454 #1]  INFO -- :
I, [2023-07-04T08:35:07.789985 #1]  INFO -- : > chown postgres:postgres /shared/postgres_run
I, [2023-07-04T08:35:07.793915 #1]  INFO -- :
I, [2023-07-04T08:35:07.794579 #1]  INFO -- : > chmod 775 /shared/postgres_run
I, [2023-07-04T08:35:07.799138 #1]  INFO -- :
I, [2023-07-04T08:35:07.799642 #1]  INFO -- : > rm -fr /var/run/postgresql
I, [2023-07-04T08:35:07.803203 #1]  INFO -- :
I, [2023-07-04T08:35:07.803670 #1]  INFO -- : > ln -s /shared/postgres_run /var/run/postgresql
I, [2023-07-04T08:35:07.806664 #1]  INFO -- :
I, [2023-07-04T08:35:07.807133 #1]  INFO -- : > socat /dev/null UNIX-CONNECT:/shared/postgres_run/.s.PGSQL.5432 || exit 0 && echo postgres already running stop container ; exit 1
2023/07/04 08:35:07 socat[18] E connect(6, AF=1 "/shared/postgres_run/.s.PGSQL.5432", 36): No such file or directory
I, [2023-07-04T08:35:07.815857 #1]  INFO -- :
I, [2023-07-04T08:35:07.816230 #1]  INFO -- : > rm -fr /shared/postgres_run/.s*
I, [2023-07-04T08:35:07.821272 #1]  INFO -- :
I, [2023-07-04T08:35:07.821753 #1]  INFO -- : > rm -fr /shared/postgres_run/*.pid
I, [2023-07-04T08:35:07.825460 #1]  INFO -- :
I, [2023-07-04T08:35:07.825846 #1]  INFO -- : > mkdir -p /shared/postgres_run/13-main.pg_stat_tmp
I, [2023-07-04T08:35:07.828773 #1]  INFO -- :
I, [2023-07-04T08:35:07.829257 #1]  INFO -- : > chown postgres:postgres /shared/postgres_run/13-main.pg_stat_tmp
I, [2023-07-04T08:35:07.831919 #1]  INFO -- :
I, [2023-07-04T08:35:07.837345 #1]  INFO -- : File > /etc/service/postgres/run  chmod: +x  chown:
I, [2023-07-04T08:35:07.843481 #1]  INFO -- : File > /etc/service/postgres/log/run  chmod: +x  chown:
I, [2023-07-04T08:35:07.850314 #1]  INFO -- : File > /etc/runit/3.d/99-postgres  chmod: +x  chown:
I, [2023-07-04T08:35:07.855908 #1]  INFO -- : File > /root/upgrade_postgres  chmod: +x  chown:
I, [2023-07-04T08:35:07.856300 #1]  INFO -- : > chown -R root /var/lib/postgresql/13/main
I, [2023-07-04T08:35:08.013507 #1]  INFO -- :
I, [2023-07-04T08:35:08.013848 #1]  INFO -- : > [ ! -e /shared/postgres_data ] && install -d -m 0755 -o postgres -g postgres /shared/postgres_data && sudo -E -u postgres /usr/lib/postgresql/13/bin/initdb -D /shared/postgres_data || exit 0
I, [2023-07-04T08:35:08.016115 #1]  INFO -- :
I, [2023-07-04T08:35:08.016262 #1]  INFO -- : > chown -R postgres:postgres /shared/postgres_data
I, [2023-07-04T08:35:08.049958 #1]  INFO -- :
I, [2023-07-04T08:35:08.050126 #1]  INFO -- : > chown -R postgres:postgres /var/run/postgresql
I, [2023-07-04T08:35:08.053008 #1]  INFO -- :
I, [2023-07-04T08:35:08.053405 #1]  INFO -- : > /root/upgrade_postgres
I, [2023-07-04T08:35:08.060826 #1]  INFO -- :
I, [2023-07-04T08:35:08.061125 #1]  INFO -- : > rm /root/upgrade_postgres
I, [2023-07-04T08:35:08.063448 #1]  INFO -- :
I, [2023-07-04T08:35:08.064215 #1]  INFO -- : Replacing data_directory = '/var/lib/postgresql/13/main' with data_directory = '/shared/postgres_data' in /etc/postgresql/13/main/postgresql.conf
I, [2023-07-04T08:35:08.064714 #1]  INFO -- : Replacing (?-mix:#?listen_addresses *=.*) with listen_addresses = '*' in /etc/postgresql/13/main/postgresql.conf
I, [2023-07-04T08:35:08.064984 #1]  INFO -- : Replacing (?-mix:#?synchronous_commit *=.*) with synchronous_commit = $db_synchronous_commit in /etc/postgresql/13/main/postgresql.conf
I, [2023-07-04T08:35:08.065291 #1]  INFO -- : Replacing (?-mix:#?shared_buffers *=.*) with shared_buffers = $db_shared_buffers in /etc/postgresql/13/main/postgresql.conf
I, [2023-07-04T08:35:08.065574 #1]  INFO -- : Replacing (?-mix:#?work_mem *=.*) with work_mem = $db_work_mem in /etc/postgresql/13/main/postgresql.conf
I, [2023-07-04T08:35:08.065849 #1]  INFO -- : Replacing (?-mix:#?default_text_search_config *=.*) with default_text_search_config = '$db_default_text_search_config' in /etc/postgresql/13/main/postgresql.conf
I, [2023-07-04T08:35:08.066118 #1]  INFO -- : > install -d -m 0755 -o postgres -g postgres /shared/postgres_backup
I, [2023-07-04T08:35:08.069168 #1]  INFO -- :
I, [2023-07-04T08:35:08.069586 #1]  INFO -- : Replacing (?-mix:#?checkpoint_segments *=.*) with checkpoint_segments = $db_checkpoint_segments in /etc/postgresql/13/main/postgresql.conf
I, [2023-07-04T08:35:08.069904 #1]  INFO -- : Replacing (?-mix:#?logging_collector *=.*) with logging_collector = $db_logging_collector in /etc/postgresql/13/main/postgresql.conf
I, [2023-07-04T08:35:08.070256 #1]  INFO -- : Replacing (?-mix:#?log_min_duration_statement *=.*) with log_min_duration_statement = $db_log_min_duration_statement in /etc/postgresql/13/main/postgresql.conf
I, [2023-07-04T08:35:08.070817 #1]  INFO -- : Replacing (?-mix:^#local +replication +postgres +peer$) with local replication postgres  peer in /etc/postgresql/13/main/pg_hba.conf
I, [2023-07-04T08:35:08.071076 #1]  INFO -- : Replacing (?-mix:^host.*all.*all.*127.*$) with host all all 0.0.0.0/0 md5 in /etc/postgresql/13/main/pg_hba.conf
I, [2023-07-04T08:35:08.071371 #1]  INFO -- : Replacing (?-mix:^host.*all.*all.*::1\/128.*$) with host all all ::/0 md5 in /etc/postgresql/13/main/pg_hba.conf
I, [2023-07-04T08:35:08.071569 #1]  INFO -- : > HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/13/bin/postmaster -D /etc/postgresql/13/main
I, [2023-07-04T08:35:08.073087 #1]  INFO -- : > sleep 5
2023-07-04 08:35:08.420 UTC [41] LOG:  starting PostgreSQL 13.11 (Debian 13.11-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2023-07-04 08:35:08.421 UTC [41] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2023-07-04 08:35:08.421 UTC [41] LOG:  listening on IPv6 address "::", port 5432
2023-07-04 08:35:08.431 UTC [41] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-07-04 08:35:08.446 UTC [44] LOG:  database system was shut down at 2023-07-04 08:31:43 UTC
2023-07-04 08:35:08.465 UTC [41] LOG:  database system is ready to accept connections
I, [2023-07-04T08:35:13.076935 #1]  INFO -- :
I, [2023-07-04T08:35:13.077237 #1]  INFO -- : > su postgres -c 'createdb discourse' || true
2023-07-04 08:35:13.149 UTC [54] postgres@postgres ERROR:  database "discourse" already exists
2023-07-04 08:35:13.149 UTC [54] postgres@postgres STATEMENT:  CREATE DATABASE discourse;
createdb: error: database creation failed: ERROR:  database "discourse" already exists
I, [2023-07-04T08:35:13.152279 #1]  INFO -- :
I, [2023-07-04T08:35:13.152523 #1]  INFO -- : > su postgres -c 'psql discourse -c "create user discourse;"' || true
2023-07-04 08:35:13.211 UTC [58] postgres@discourse ERROR:  role "discourse" already exists
2023-07-04 08:35:13.211 UTC [58] postgres@discourse STATEMENT:  create user discourse;
ERROR:  role "discourse" already exists
I, [2023-07-04T08:35:13.213860 #1]  INFO -- :
I, [2023-07-04T08:35:13.214061 #1]  INFO -- : > su postgres -c 'psql discourse -c "grant all privileges on database discourse to discourse;"' || true
I, [2023-07-04T08:35:13.265307 #1]  INFO -- : GRANT

I, [2023-07-04T08:35:13.265564 #1]  INFO -- : > su postgres -c 'psql discourse -c "alter schema public owner to discourse;"'
I, [2023-07-04T08:35:13.317945 #1]  INFO -- : ALTER SCHEMA

I, [2023-07-04T08:35:13.318152 #1]  INFO -- : > su postgres -c 'psql template1 -c "create extension if not exists hstore;"'
NOTICE:  extension "hstore" already exists, skipping
I, [2023-07-04T08:35:13.374925 #1]  INFO -- : CREATE EXTENSION

I, [2023-07-04T08:35:13.375085 #1]  INFO -- : > su postgres -c 'psql template1 -c "create extension if not exists pg_trgm;"'
NOTICE:  extension "pg_trgm" already exists, skipping
I, [2023-07-04T08:35:13.424029 #1]  INFO -- : CREATE EXTENSION

I, [2023-07-04T08:35:13.424239 #1]  INFO -- : > su postgres -c 'psql discourse -c "create extension if not exists hstore;"'
NOTICE:  extension "hstore" already exists, skipping
I, [2023-07-04T08:35:13.473016 #1]  INFO -- : CREATE EXTENSION

I, [2023-07-04T08:35:13.473353 #1]  INFO -- : > su postgres -c 'psql discourse -c "create extension if not exists pg_trgm;"'
NOTICE:  extension "pg_trgm" already exists, skipping
I, [2023-07-04T08:35:13.521434 #1]  INFO -- : CREATE EXTENSION

I, [2023-07-04T08:35:13.521788 #1]  INFO -- : > sudo -u postgres psql discourse
I, [2023-07-04T08:35:13.524205 #1]  INFO -- : update pg_database set encoding = pg_char_to_encoding('UTF8') where datname = 'discourse' AND encoding = pg_char_to_encoding('SQL_ASCII');

I, [2023-07-04T08:35:13.584880 #1]  INFO -- : File > /var/lib/postgresql/take-database-backup  chmod: +x  chown: postgres:postgres
I, [2023-07-04T08:35:13.588081 #1]  INFO -- : File > /var/spool/cron/crontabs/postgres  chmod:   chown:
I, [2023-07-04T08:35:13.588556 #1]  INFO -- : > echo postgres installed!
I, [2023-07-04T08:35:13.591048 #1]  INFO -- : postgres installed!

I, [2023-07-04T08:35:13.596241 #1]  INFO -- : File > /etc/service/redis/run  chmod: +x  chown:
I, [2023-07-04T08:35:13.601338 #1]  INFO -- : File > /etc/service/redis/log/run  chmod: +x  chown:
I, [2023-07-04T08:35:13.606793 #1]  INFO -- : File > /etc/runit/3.d/10-redis  chmod: +x  chown:
I, [2023-07-04T08:35:13.608119 #1]  INFO -- : Replacing daemonize yes with  in /etc/redis/redis.conf
I, [2023-07-04T08:35:13.609135 #1]  INFO -- : Replacing (?-mix:^pidfile.*$) with  in /etc/redis/redis.conf
I, [2023-07-04T08:35:13.609825 #1]  INFO -- : > install -d -m 0755 -o redis -g redis /shared/redis_data
I, [2023-07-04T08:35:13.613120 #1]  INFO -- :
I, [2023-07-04T08:35:13.614135 #1]  INFO -- : Replacing (?-mix:^logfile.*$) with logfile "" in /etc/redis/redis.conf
I, [2023-07-04T08:35:13.614898 #1]  INFO -- : Replacing (?-mix:^bind .*$) with  in /etc/redis/redis.conf
I, [2023-07-04T08:35:13.615551 #1]  INFO -- : Replacing (?-mix:^dir .*$) with dir /shared/redis_data in /etc/redis/redis.conf
I, [2023-07-04T08:35:13.616281 #1]  INFO -- : Replacing (?-mix:^protected-mode yes) with protected-mode no in /etc/redis/redis.conf
I, [2023-07-04T08:35:13.616974 #1]  INFO -- : Replacing # io-threads 4 with io-threads $redis_io_threads in /etc/redis/redis.conf
I, [2023-07-04T08:35:13.617567 #1]  INFO -- : > echo redis installed
I, [2023-07-04T08:35:13.620142 #1]  INFO -- : redis installed

I, [2023-07-04T08:35:13.620773 #1]  INFO -- : > cat /etc/redis/redis.conf | grep logfile
I, [2023-07-04T08:35:13.627103 #1]  INFO -- : logfile ""

I, [2023-07-04T08:35:13.627893 #1]  INFO -- : > exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf
I, [2023-07-04T08:35:13.629707 #1]  INFO -- : > sleep 10
102:C 04 Jul 2023 08:35:13.639 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
102:C 04 Jul 2023 08:35:13.639 # Redis version=7.0.7, bits=64, commit=00000000, modified=0, pid=102, just started
102:C 04 Jul 2023 08:35:13.639 # Configuration loaded
102:M 04 Jul 2023 08:35:13.639 * monotonic clock: POSIX clock_gettime
102:M 04 Jul 2023 08:35:13.640 * Running mode=standalone, port=6379.
102:M 04 Jul 2023 08:35:13.640 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
102:M 04 Jul 2023 08:35:13.640 # Server initialized
102:M 04 Jul 2023 08:35:13.640 * Loading RDB produced by version 7.0.7
102:M 04 Jul 2023 08:35:13.640 * RDB age 211 seconds
102:M 04 Jul 2023 08:35:13.640 * RDB memory usage when created 15.65 Mb
102:M 04 Jul 2023 08:35:13.681 * Done loading RDB, keys loaded: 11320, keys expired: 0.
102:M 04 Jul 2023 08:35:13.681 * DB loaded from disk: 0.041 seconds
102:M 04 Jul 2023 08:35:13.681 * Ready to accept connections
I, [2023-07-04T08:35:23.632444 #1]  INFO -- :
I, [2023-07-04T08:35:23.634001 #1]  INFO -- : > thpoff echo "thpoff is installed!"
I, [2023-07-04T08:35:23.647427 #1]  INFO -- : thpoff is installed!

I, [2023-07-04T08:35:23.648579 #1]  INFO -- : > /usr/local/bin/ruby -e 'if ENV["DISCOURSE_SMTP_ADDRESS"] == "smtp.example.com"; puts "Aborting! Mail is not configured!"; exit 1; end'
I, [2023-07-04T08:35:23.734677 #1]  INFO -- :
I, [2023-07-04T08:35:23.734943 #1]  INFO -- : > /usr/local/bin/ruby -e 'if ENV["DISCOURSE_HOSTNAME"] == "discourse.example.com"; puts "Aborting! Domain is not configured!"; exit 1; end'
I, [2023-07-04T08:35:23.805114 #1]  INFO -- :
I, [2023-07-04T08:35:23.805363 #1]  INFO -- : > /usr/local/bin/ruby -e 'if (ENV["DISCOURSE_CDN_URL"] || "")[0..1] == "//"; puts "Aborting! CDN must have a protocol specified. Once fixed you should rebake your posts now to correct all posts."; exit 1; end'
I, [2023-07-04T08:35:23.875870 #1]  INFO -- :
I, [2023-07-04T08:35:23.876109 #1]  INFO -- : > rm -f /etc/cron.d/anacron
I, [2023-07-04T08:35:23.879621 #1]  INFO -- :
I, [2023-07-04T08:35:23.883359 #1]  INFO -- : File > /etc/cron.d/anacron  chmod:   chown:
I, [2023-07-04T08:35:23.889667 #1]  INFO -- : File > /etc/runit/1.d/copy-env  chmod: +x  chown:
I, [2023-07-04T08:35:23.895348 #1]  INFO -- : File > /etc/service/unicorn/run  chmod: +x  chown:
I, [2023-07-04T08:35:23.900664 #1]  INFO -- : File > /etc/service/nginx/run  chmod: +x  chown:
I, [2023-07-04T08:35:23.906591 #1]  INFO -- : File > /etc/runit/3.d/01-nginx  chmod: +x  chown:
I, [2023-07-04T08:35:23.911796 #1]  INFO -- : File > /etc/runit/3.d/02-unicorn  chmod: +x  chown:
I, [2023-07-04T08:35:23.912015 #1]  INFO -- : Replacing # postgres with sv start postgres || exit 1 in /etc/service/unicorn/run
I, [2023-07-04T08:35:23.912204 #1]  INFO -- : > exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf
I, [2023-07-04T08:35:23.914896 #1]  INFO -- : > cd /var/www/discourse && sudo -H -E -u discourse git reset --hard
129:C 04 Jul 2023 08:35:23.923 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
129:C 04 Jul 2023 08:35:23.923 # Redis version=7.0.7, bits=64, commit=00000000, modified=0, pid=129, just started
129:C 04 Jul 2023 08:35:23.923 # Configuration loaded
129:M 04 Jul 2023 08:35:23.923 * monotonic clock: POSIX clock_gettime
129:M 04 Jul 2023 08:35:23.923 # Warning: Could not create server TCP listening socket *:6379: bind: Address already in use
129:M 04 Jul 2023 08:35:23.923 # Failed listening on port 6379 (TCP), aborting.
Updating files: 100% (33396/33396), done.
I, [2023-07-04T08:35:28.224120 #1]  INFO -- : HEAD is now at 3f1024de7 DEV: Refactor DM channel creation into new service pattern (#22144)

I, [2023-07-04T08:35:28.224329 #1]  INFO -- : > cd /var/www/discourse && sudo -H -E -u discourse git clean -f
I, [2023-07-04T08:35:28.441174 #1]  INFO -- :
I, [2023-07-04T08:35:28.441741 #1]  INFO -- : > cd /var/www/discourse && sudo -H -E -u discourse bash -c '
  set -o errexit
  if [ $(git rev-parse --is-shallow-repository) == "true" ]; then
      git remote set-branches --add origin main
      git remote set-branches origin stable
      git fetch --depth 1 origin stable
  else
      git fetch --tags --prune-tags --prune --force origin
  fi
'
From https://github.com/discourse/discourse
 - [deleted]             (none)     -> origin/0-drop-sk-test
 - [deleted]             (none)     -> origin/dev/move-chat-user-count-update-to-ensure-consistency
 - [deleted]             (none)     -> origin/dev_update_diffhtml
 - [deleted]             (none)     -> origin/fix-intercept-with-target
 - [deleted]             (none)     -> origin/issue/font-loading-wizard-style
 - [deleted]             (none)     -> origin/modal-named-outlet
   3f1024de7..ee1dbd46c  main                  -> origin/main
 * [new branch]          0-helpers             -> origin/0-helpers
 + a23a31600...e24fcb507 activation-modals-update -> origin/activation-modals-update  (forced update)
   95ce96528..d370c8c0e  chat-notices          -> origin/chat-notices
 * [new branch]          dependabot/npm_and_yarn/app/assets/javascripts/uppy/aws-s3-3.2.0 -> origin/dependabot/npm_and_yarn/app/assets/javascripts/uppy/aws-s3-3.2.0
 + 86e63992b...3ab4d8598 dependabot/npm_and_yarn/app/assets/javascripts/uppy/aws-s3-multipart-3.4.0 -> origin/dependabot/npm_and_yarn/app/assets/javascripts/uppy/aws-s3-multipart-3.4.0  (forced update)
 + 3949f2ca8...e71e5eff6 dev/make-sure-we-stream-data-to-csv-files-when-running-exports -> origin/dev/make-sure-we-stream-data-to-csv-files-when-running-exports  (forced update)
 * [new branch]          dev/minio-s3-system-specs -> origin/dev/minio-s3-system-specs
 + dff30f62e...e8082afe2 dismiss-modals-update -> origin/dismiss-modals-update  (forced update)
 * [new branch]          do-not-disturb-modal-upgrade -> origin/do-not-disturb-modal-upgrade
 * [new branch]          feature/interpolation-key-check -> origin/feature/interpolation-key-check
   33608240f..509797feb  feature/tracking-unread-thread-in-sidebar -> origin/feature/tracking-unread-thread-in-sidebar
   e571e1131..4fae425b9  fix-mobile-share      -> origin/fix-mobile-share
 + f588c592d...03e460b6a fullscreen-modals-update -> origin/fullscreen-modals-update  (forced update)
 + ccc6c903a...94bb20818 group-add-members-modal-upgrade -> origin/group-add-members-modal-upgrade  (forced update)
 * [new branch]          issue/thread-original-message-delete-restore -> origin/issue/thread-original-message-delete-restore
 + 1980b69ef...67273d209 loic-migrate-chat-message-creator-to-a-service -> origin/loic-migrate-chat-message-creator-to-a-service  (forced update)
 + d1588f61c...c07b70d74 poll-plugin-update    -> origin/poll-plugin-update  (forced update)
   136013353..b83369a54  poll-refactor         -> origin/poll-refactor
 + 12f2d7ff7...7717f3651 second-factor-add-security-key-modal-upgrade -> origin/second-factor-add-security-key-modal-upgrade  (forced update)
 + 205f3bf1b...e99d456be second-factor-add-totp-modal-upgrade -> origin/second-factor-add-totp-modal-upgrade  (forced update)
 + dc2c6cc41...696652aa0 second-factor-backup-edit-modal-upgrade -> origin/second-factor-backup-edit-modal-upgrade  (forced update)
 + f904e4133...9d65daa00 second-factor-edit-security-key-modal-upgrade -> origin/second-factor-edit-security-key-modal-upgrade  (forced update)
 + 9d0d76101...ad2ae96f0 share-topic-modal     -> origin/share-topic-modal  (forced update)
 + 310137e3c...d9b37147c slack_import          -> origin/slack_import  (forced update)
   7de3cb9b0..38a9694ff  tests-passed          -> origin/tests-passed
I, [2023-07-04T08:35:30.181323 #1]  INFO -- :
I, [2023-07-04T08:35:30.181801 #1]  INFO -- : > cd /var/www/discourse && sudo -H -E -u discourse bash -c '
  set -o errexit
  if [[ $(git symbolic-ref --short HEAD) == stable ]] ; then
      git pull
  else
      git -c advice.detachedHead=false checkout stable
  fi
'
Switched to a new branch 'stable'
I, [2023-07-04T08:35:36.709492 #1]  INFO -- : Branch 'stable' set up to track remote branch 'stable' from 'origin'.

I, [2023-07-04T08:35:36.709921 #1]  INFO -- : > cd /var/www/discourse && sudo -H -E -u discourse git config user.discourse-version stable
I, [2023-07-04T08:35:36.722428 #1]  INFO -- :
I, [2023-07-04T08:35:36.722824 #1]  INFO -- : > cd /var/www/discourse && mkdir -p tmp
I, [2023-07-04T08:35:36.726861 #1]  INFO -- :
I, [2023-07-04T08:35:36.727244 #1]  INFO -- : > cd /var/www/discourse && chown discourse:www-data tmp
I, [2023-07-04T08:35:36.730932 #1]  INFO -- :
I, [2023-07-04T08:35:36.731353 #1]  INFO -- : > cd /var/www/discourse && mkdir -p tmp/pids
I, [2023-07-04T08:35:36.735322 #1]  INFO -- :
I, [2023-07-04T08:35:36.735760 #1]  INFO -- : > cd /var/www/discourse && mkdir -p tmp/sockets
I, [2023-07-04T08:35:36.739494 #1]  INFO -- :
I, [2023-07-04T08:35:36.739901 #1]  INFO -- : > cd /var/www/discourse && touch tmp/.gitkeep
I, [2023-07-04T08:35:36.744366 #1]  INFO -- :
I, [2023-07-04T08:35:36.744815 #1]  INFO -- : > cd /var/www/discourse && mkdir -p                    /shared/log/rails
I, [2023-07-04T08:35:36.748457 #1]  INFO -- :
I, [2023-07-04T08:35:36.748854 #1]  INFO -- : > cd /var/www/discourse && bash -c "touch -a           /shared/log/rails/{production,production_errors,unicorn.stdout,unicorn.stderr,sidekiq}.log"
I, [2023-07-04T08:35:36.754083 #1]  INFO -- :
I, [2023-07-04T08:35:36.754569 #1]  INFO -- : > cd /var/www/discourse && bash -c "ln    -s           /shared/log/rails/{production,production_errors,unicorn.stdout,unicorn.stderr,sidekiq}.log /var/www/discourse/log"
I, [2023-07-04T08:35:36.760285 #1]  INFO -- :
I, [2023-07-04T08:35:36.760700 #1]  INFO -- : > cd /var/www/discourse && bash -c "mkdir -p           /shared/{uploads,backups}"
I, [2023-07-04T08:35:36.766617 #1]  INFO -- :
I, [2023-07-04T08:35:36.767172 #1]  INFO -- : > cd /var/www/discourse && bash -c "ln    -s           /shared/{uploads,backups} /var/www/discourse/public"
I, [2023-07-04T08:35:36.776053 #1]  INFO -- :
I, [2023-07-04T08:35:36.776610 #1]  INFO -- : > cd /var/www/discourse && bash -c "mkdir -p           /shared/tmp/{backups,restores}"
I, [2023-07-04T08:35:36.782478 #1]  INFO -- :
I, [2023-07-04T08:35:36.783022 #1]  INFO -- : > cd /var/www/discourse && bash -c "ln    -s           /shared/tmp/{backups,restores} /var/www/discourse/tmp"
I, [2023-07-04T08:35:36.788665 #1]  INFO -- :
I, [2023-07-04T08:35:36.789017 #1]  INFO -- : > cd /var/www/discourse && chown -R discourse:www-data /shared/log/rails /shared/uploads /shared/backups /shared/tmp
I, [2023-07-04T08:35:36.905317 #1]  INFO -- :
I, [2023-07-04T08:35:36.905593 #1]  INFO -- : > cd /var/www/discourse && [ ! -d public/plugins ] || find public/plugins/ -maxdepth 1 -xtype l -delete
I, [2023-07-04T08:35:36.908220 #1]  INFO -- :
I, [2023-07-04T08:35:36.908848 #1]  INFO -- : Replacing # redis with sv start redis || exit 1 in /etc/service/unicorn/run
I, [2023-07-04T08:35:36.909446 #1]  INFO -- : > cd /var/www/discourse/plugins && mkdir -p plugins
I, [2023-07-04T08:35:36.913315 #1]  INFO -- :
I, [2023-07-04T08:35:36.913811 #1]  INFO -- : > cd /var/www/discourse/plugins && git clone https://github.com/discourse/docker_manager.git
Cloning into 'docker_manager'...
I, [2023-07-04T08:35:38.642193 #1]  INFO -- :
I, [2023-07-04T08:35:38.642814 #1]  INFO -- : > cp /var/www/discourse/config/nginx.sample.conf /etc/nginx/conf.d/discourse.conf
I, [2023-07-04T08:35:38.647323 #1]  INFO -- :
I, [2023-07-04T08:35:38.647896 #1]  INFO -- : > rm /etc/nginx/sites-enabled/default
I, [2023-07-04T08:35:38.650756 #1]  INFO -- :
I, [2023-07-04T08:35:38.651170 #1]  INFO -- : > mkdir -p /var/nginx/cache
I, [2023-07-04T08:35:38.654148 #1]  INFO -- :
I, [2023-07-04T08:35:38.654989 #1]  INFO -- : Replacing pid /run/nginx.pid; with daemon off; in /etc/nginx/nginx.conf
I, [2023-07-04T08:35:38.655476 #1]  INFO -- : Replacing (?m-ix:upstream[^\}]+\}) with upstream discourse { server 127.0.0.1:3000; } in /etc/nginx/conf.d/discourse.conf
I, [2023-07-04T08:35:38.655887 #1]  INFO -- : Replacing (?-mix:server_name.+$) with server_name _ ; in /etc/nginx/conf.d/discourse.conf
I, [2023-07-04T08:35:38.656346 #1]  INFO -- : Replacing (?-mix:client_max_body_size.+$) with client_max_body_size $upload_size ; in /etc/nginx/conf.d/discourse.conf
I, [2023-07-04T08:35:38.656706 #1]  INFO -- : Replacing (?-mix:worker_connections.+$) with worker_connections $nginx_worker_connections ; in /etc/nginx/nginx.conf
I, [2023-07-04T08:35:38.656972 #1]  INFO -- : > echo "done configuring web"
I, [2023-07-04T08:35:38.659032 #1]  INFO -- : done configuring web

I, [2023-07-04T08:35:38.659502 #1]  INFO -- : > cd /var/www/discourse && gem install bundler --conservative -v $(awk '/BUNDLED WITH/ { getline; gsub(/ /,""); print $0 }' Gemfile.lock)
I, [2023-07-04T08:35:39.376540 #1]  INFO -- : Successfully installed bundler-2.4.1
1 gem installed

I, [2023-07-04T08:35:39.376897 #1]  INFO -- : > cd /var/www/discourse && find /var/www/discourse ! -user discourse -exec chown discourse {} \+
I, [2023-07-04T08:35:42.247035 #1]  INFO -- :
I, [2023-07-04T08:35:42.247550 #1]  INFO -- : > cd /var/www/discourse && su discourse -c 'yarn install --frozen-lockfile && yarn cache clean'
warning " > @mixer/parallel-prettier@2.0.3" has unmet peer dependency "prettier@^2.0.0".
warning "eslint-config-discourse > eslint-plugin-lodash@7.1.0" has unmet peer dependency "lodash@>=4".
I, [2023-07-04T08:37:51.032227 #1]  INFO -- : yarn install v1.22.19
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
[4/5] Linking dependencies...
[5/5] Building fresh packages...
$ yarn --cwd app/assets/javascripts/discourse $(node -e 'if(JSON.parse(process.env.npm_config_argv).original.includes(`--frozen-lockfile`)){console.log(`--frozen-lockfile`)}')
yarn install v1.22.19
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
Done in 68.15s.
Done in 118.83s.
yarn cache v1.22.19
success Cleared cache.
Done in 9.49s.

I, [2023-07-04T08:37:51.033163 #1]  INFO -- : > cd /var/www/discourse && su discourse -c 'bundle config --local deployment true'
I, [2023-07-04T08:37:51.285818 #1]  INFO -- :
I, [2023-07-04T08:37:51.285947 #1]  INFO -- : > cd /var/www/discourse && su discourse -c 'bundle config --local without "development test"'
I, [2023-07-04T08:37:51.480721 #1]  INFO -- : You are replacing the current local value of without, which is currently "test:development"

Se ha producido un error en mi actualización

```ruby
api_key = "a quick brown fox"
fetch("https://api.example.com/data", headers: { 'Authorization' => api_key })

Por favor, ayúdame a solucionarlo.

¡Nos alegra mucho que estés aquí! ¿Quieres ejecutar tu propio servidor de Minecraft? Haz clic en el botón “Comenzar” a continuación; es muy fácil.

He propuesto una llamada arquitectura limpia para el nuevo servicio. Pero limpio no siempre significa simple.

Ha habido un error en mi actualización

api_key = "a quick brown fox"
fetch("https://api.example.com/data", headers: { 'Authorization' => api_key })

Por favor, ayúdame a solucionarlo.

I, [2023-07-04T08:37:51.481286 #1] INFO – : > cd /var/www/discourse && su discourse -c ‘bundle install --retry 3 --jobs 4’
I, [2023-07-04T08:40:20.584190 #1] INFO – : Obteniendo metadatos de gemas de https://rubygems.org/
Obteniendo GitHub - discourse/mail: A Really Ruby Mail Library · GitHub
Usando rake 13.0.6
Obteniendo concurrent-ruby 1.1.10
Obteniendo minitest 5.17.0
Usando builder 3.2.4
Usando racc 1.6.2
Obteniendo erubi 1.11.0
Usando crass 1.0.6
Obteniendo rack 2.2.5
Instalando erubi 1.11.0
Instalando minitest 5.17.0
Instalando rack 2.2.5
Usando mini_mime 1.1.2
Usando timeout 0.3.1
Usando public_suffix 5.0.1
Usando aws-eventstream 1.2.0
Usando aws-partitions 1.583.0
Usando jmespath 1.6.2
Obteniendo msgpack 1.6.0
Usando bundler 2.4.1
Usando byebug 11.1.3
Usando cbor 0.5.9.6
Usando cgi 0.3.6
Usando chunky_png 1.4.0
Usando coderay 1.1.3
Usando colored2 3.1.2
Obteniendo connection_pool 2.3.0
Instalando concurrent-ruby 1.1.10
Instalando msgpack 1.6.0 con extensiones nativas
Instalando connection_pool 2.3.0
Obteniendo openssl 3.0.2
Instalando openssl 3.0.2 con extensiones nativas
Usando cppjieba_rb 0.4.2
Usando diffy 3.4.2
Usando digest 3.1.1
Usando discourse-fonts 0.0.9
Obteniendo regexp_parser 2.6.1
Instalando regexp_parser 2.6.1
Usando email_reply_trimmer 0.1.13
Obteniendo excon 0.96.0
Usando execjs 2.8.1
Obteniendo exifr 1.3.10
Instalando exifr 1.3.10
Instalando excon 0.96.0
Usando faraday-net_http 3.0.2
Usando ruby2_keywords 0.0.5
Usando fast_blank 1.0.1
Usando fast_xs 0.8.0
Obteniendo fastimage 2.2.6
Usando ffi 1.15.5
Instalando fastimage 2.2.6
Usando fspath 3.1.2
Usando gc_tracer 1.5.1
Usando guess_html_encoding 0.0.11
Usando hana 1.3.7
Usando hashie 5.0.0
Usando highline 2.1.0
Usando hkdf 1.0.0
Usando http_accept_language 2.1.1
Obteniendo image_size 3.2.0
Usando htmlentities 4.3.4
Usando in_threads 1.6.0
Usando progress 3.6.0
Usando json 2.6.3
Obteniendo uri_template 0.7.0
Instalando uri_template 0.7.0
Instalando image_size 3.2.0
Obteniendo jwt 2.6.0
Instalando jwt 2.6.0
Usando kgio 2.11.4
Obteniendo libv8-node 16.10.0.0 (x86_64-linux)
Usando method_source 1.0.0
Obteniendo thor 1.2.1
Instalando thor 1.2.1
Obteniendo zeitwerk 2.6.6
Instalando zeitwerk 2.6.6
Usando logstash-event 1.2.02
Obteniendo logster 2.11.3
Instalando logster 2.11.3
Usando lru_redux 1.1.0
Usando lz4-ruby 0.3.3
Usando maxminddb 0.1.22
Usando memory_profiler 1.0.1
Obteniendo redis 4.8.0
Instalando redis 4.8.0
Usando mini_sql 1.4.0
Usando multi_json 1.15.0
Usando multi_xml 0.6.0
Usando mustache 1.1.1
Usando uri 0.12.2
Obteniendo nio4r 2.5.8
Instalando nio4r 2.5.8 con extensiones nativas
Instalando libv8-node 16.10.0.0 (x86_64-linux)
Obteniendo version_gem 1.1.1
Instalando version_gem 1.1.1
Obteniendo oj 3.13.14
Instalando oj 3.13.14 con extensiones nativas
Usando optimist 3.0.1
Obteniendo pg 1.4.5
Instalando pg 1.4.5 con extensiones nativas
Obteniendo r2 0.2.7
Instalando r2 0.2.7
Obteniendo raindrops 0.20.0
Instalando raindrops 0.20.0 con extensiones nativas
Usando rchardet 1.8.0
Usando rexml 3.2.5
Usando rinku 2.0.6
Usando rotp 6.2.2
Usando rqrcode_core 1.2.0
Usando rubyzip 2.3.2
Obteniendo tilt 2.0.11
Instalando tilt 2.0.11
Usando sshkey 2.0.0
Obteniendo stackprof 0.2.23
Instalando stackprof 0.2.23 con extensiones nativas
Usando unf_ext 0.0.8.2
Usando webrick 1.7.0
Obteniendo xorcist 1.1.3
Instalando xorcist 1.1.3 con extensiones nativas
Obteniendo nokogiri 1.14.2 (x86_64-linux)
Instalando nokogiri 1.14.2 (x86_64-linux)
Usando mail 2.8.0.edge desde GitHub - discourse/mail: A Really Ruby Mail Library · GitHub (en main@5b700fc)
Usando net-protocol 0.2.1
Obteniendo addressable 2.8.1
Instalando addressable 2.8.1
Usando aws-sigv4 1.5.0
Obteniendo rack-test 2.0.2
Instalando rack-test 2.0.2
Usando request_store 1.5.1
Obteniendo message_bus 4.3.1
Instalando message_bus 4.3.1
Obteniendo rack-mini-profiler 3.0.0
Instalando rack-mini-profiler 3.0.0
Obteniendo rack-protection 3.0.5
Instalando rack-protection 3.0.5
Obteniendo i18n 1.12.0
Instalando i18n 1.12.0
Obteniendo tzinfo 2.0.5
Instalando tzinfo 2.0.5
Obteniendo sprockets 3.7.2
Instalando sprockets 3.7.2
Obteniendo ecma-re-validator 0.4.0
Instalando ecma-re-validator 0.4.0
Usando uglifier 4.2.0
Obteniendo faraday 2.7.2
Instalando faraday 2.7.2
Usando mini_suffix 0.3.3
Obteniendo sassc 2.0.1
Instalando sassc 2.0.1 con extensiones nativas
Usando omniauth 1.9.2
Obteniendo image_optim 0.31.2
Instalando image_optim 0.31.2
Usando pry 0.14.2
Usando logstash-logger 0.26.1
Obteniendo sidekiq 6.5.8
Instalando sidekiq 6.5.8
Obteniendo redis-namespace 1.9.0
Instalando redis-namespace 1.9.0
Usando net-http 0.3.2
Obteniendo mini_racer 0.6.3
Instalando mini_racer 0.6.3 con extensiones nativas
Usando oauth-tty 1.0.5
Usando snaky_hash 2.0.1
Obteniendo bootsnap 1.15.0
Instalando bootsnap 1.15.0 con extensiones nativas
Usando rbtrace 0.4.14
Obteniendo puma 6.0.2
Instalando puma 6.0.2 con extensiones nativas
Obteniendo rqrcode 2.1.2
Instalando rqrcode 2.1.2
Usando rss 0.2.9
Usando unf 0.1.4
Obteniendo loofah 2.19.1
Instalando loofah 2.19.1
Usando ruby-readability 0.7.0
Obteniendo sanitize 6.0.0
Instalando sanitize 6.0.0
Obteniendo net-imap 0.3.1
Instalando net-imap 0.3.1
Usando net-pop 0.1.2
Usando net-smtp 0.3.3
Obteniendo css_parser 1.13.0
Instalando css_parser 1.13.0
Usando aws-sdk-core 3.130.2
Obteniendo activesupport 7.0.4.3
Instalando activesupport 7.0.4.3
Obteniendo json_schemer 0.2.23
Instalando json_schemer 0.2.23
Obteniendo faraday-retry 2.0.0
Instalando faraday-retry 2.0.0
Usando oauth2 1.4.11
Usando pry-byebug 3.10.1
Usando pry-rails 0.3.9
Obteniendo mini_scheduler 0.15.0
Instalando mini_scheduler 0.15.0
Usando unicorn 6.1.0
Usando oauth 1.1.0
Obteniendo rails-html-sanitizer 1.5.0
Instalando rails-html-sanitizer 1.5.0
Usando aws-sdk-kms 1.56.0
Usando aws-sdk-sns 1.53.0
Obteniendo rails-dom-testing 2.0.3
Instalando rails-dom-testing 2.0.3
Obteniendo globalid 1.0.1
Instalando globalid 1.0.1
Obteniendo activemodel 7.0.4.3
Instalando activemodel 7.0.4.3
Usando omniauth-oauth2 1.7.3
Usando omniauth-oauth 1.2.0
Usando aws-sdk-s3 1.114.0
Obteniendo actionview 7.0.4.3
Instalando actionview 7.0.4.3
Obteniendo activejob 7.0.4.3
Instalando activejob 7.0.4.3
Usando active_model_serializers 0.8.4
Obteniendo activerecord 7.0.4.3
Instalando activerecord 7.0.4.3
Usando omniauth-facebook 9.0.0
Usando omniauth-github 1.4.0
Usando omniauth-google-oauth2 0.8.2
Usando omniauth-twitter 1.4.0
Obteniendo actionpack 7.0.4.3
Instalando actionpack 7.0.4.3
Usando actionview_precompiler 0.2.3
Usando discourse-seed-fu 2.3.12
Obteniendo actionmailer 7.0.4.3
Instalando actionmailer 7.0.4.3
Obteniendo railties 7.0.4.3
Instalando railties 7.0.4.3
Usando sprockets-rails 3.4.2
Usando lograge 0.12.0
Obteniendo rails_failover 0.8.1
Obteniendo rails_multisite 4.0.1
Instalando rails_multisite 4.0.1
Instalando rails_failover 0.8.1
Obteniendo openssl-signature_algorithm 1.2.1
Usando web-push 3.0.0
Instalando openssl-signature_algorithm 1.2.1
Usando cose 1.3.0
Obteniendo sassc-rails 2.1.2
Instalando sassc-rails 2.1.2
¡Paquete completo! 135 dependencias de Gemfile, 171 gemas instaladas ahora.
Las gemas de los grupos ‘development’ y ‘test’ no se instalaron.
Las gemas empaquetadas se instalan en ./vendor/bundle
Mensaje post-instalación de image_optim:
La optimización de activos de imagen de Rails se ha extraído a la gema image_optim_rails
Puedes eliminar con seguridad config.assets.image_optim = false si no vas a usar esa gema

I, [2023-07-04T08:40:20.585621 #1] INFO – : > cd /var/www/discourse && su discourse -c ‘LOAD_PLUGINS=0 bundle exec rake plugin:pull_compatible_all’
I, [2023-07-04T08:40:24.327439 #1] INFO – : verificando versión compatible de docker_manager: 1b2d7eb0369155b6442b09adfb17b8942c04b093
HEAD está ahora en 1b2d7eb Actualizar versiones mínimas

I, [2023-07-04T08:40:24.327817 #1] INFO – : > cd /var/www/discourse && su discourse -c ‘bundle exec rake db:migrate’
102:M 04 Jul 2023 08:40:28.803 * 100 cambios en 300 segundos. Guardando…
102:M 04 Jul 2023 08:40:28.804 * Guardado en segundo plano iniciado por pid 2319
2319:C 04 Jul 2023 08:40:29.127 * BD guardada en disco
2319:C 04 Jul 2023 08:40:29.128 * Fork CoW para RDB: actual 1 MB, pico 1 MB, promedio 1 MB
102:M 04 Jul 2023 08:40:29.210 * Guardado en segundo plano terminado con éxito
I, [2023-07-04T08:40:29.966284 #1] INFO – :
I, [2023-07-04T08:40:29.967083 #1] INFO – : > cd /var/www/discourse && su discourse -c ‘bundle exec rake themes:update assets:precompile’

  • Construyendo
  • Construyendo
  • construyendo…
  • limpiando
  • limpiando
    Error de compilación (broccoli-persistent-filter:Babel > [Babel: @ember/test-helpers]) en @ember/test-helpers/-internal/build-registry.js

[BABEL]: — PAQUETE PLACEHOLDER —
Esta versión de @babel/plugin-proposal-private-property-in-object no está diseñada
para ser importada. Algo está importando
@babel/plugin-proposal-private-property-in-object sin declararlo en sus
dependencias (o devDependencies) en el archivo package.json.
Agrega “@babel/plugin-proposal-private-property-in-object” a tus devDependencies
para solucionar este error. Esto hará que este mensaje desaparezca.
(Mientras se procesa: /var/www/discourse/app/assets/javascripts/node_modules/@babel/preset-env/lib/index.js)Error: [BABEL]: — PAQUETE PLACEHOLDER —
Esta versión de @babel/plugin-proposal-private-property-in-object no está diseñada
para ser importada. Algo está importando
@babel/plugin-proposal-private-property-in-object sin declararlo en sus
dependencias (o devDependencies) en el archivo package.json.
Agrega “@babel/plugin-proposal-private-property-in-object” a tus devDependencies
para solucionar este error. Esto hará que este mensaje desaparezca.
(Mientras se procesa: /var/www/discourse/app/assets/javascripts/node_modules/@babel/preset-env/lib/index.js)
at Object. (/var/www/discourse/app/assets/javascripts/node_modules/@babel/preset-env/node_modules/@babel/plugin-proposal-private-property-in-object/lib/index.js:28:7)
at Module._compile (node:internal/modules/cjs/loader:1256:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
at Module.load (node:internal/modules/cjs/loader:1119:32)
at Module._load (node:internal/modules/cjs/loader:960:12)
at Module.require (node:internal/modules/cjs/loader:1143:19)
at require (node:internal/modules/cjs/helpers:110:18)
at Object. (/var/www/discourse/app/assets/javascripts/node_modules/@babel/preset-env/lib/available-plugins.js:62:46)
at Module._compile (node:internal/modules/cjs/loader:1256:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
at Module.load (node:internal/modules/cjs/loader:1119:32)
at Module._load (node:internal/modules/cjs/loader:960:12)
at Module.require (node:internal/modules/cjs/loader:1143:19)
at require (node:internal/modules/cjs/helpers:110:18)
at Object. (/var/www/discourse/app/assets/javascripts/node_modules/@babel/preset-env/lib/filter-items.js:11:25)
at Module._compile (node:internal/modules/cjs/loader:1256:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
at Module.load (node:internal/modules/cjs/loader:1119:32)
at Module._load (node:internal/modules/cjs/loader:960:12)
at Module.require (node:internal/modules/cjs/loader:1143:19)
at require (node:internal/modules/cjs/helpers:110:18)
at Object. (/var/www/discourse/app/assets/javascripts/node_modules/@babel/preset-env/lib/index.js:16:20)
at Module._compile (node:internal/modules/cjs/loader:1256:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
at Module.load (node:internal/modules/cjs/loader:1119:32)
at Module._load (node:internal/modules/cjs/loader:960:12)
at Module.require (node:internal/modules/cjs/loader:1143:19)
at require (node:internal/modules/cjs/helpers:110:18)

Traza de pila e informe de error: /tmp/error.dump.62bb2ff34bdbec58308fd7d5b2fab0f6.log
error El comando falló con código de salida 1.
I, [2023-07-04T08:40:44.826892 #1] INFO – : Comprobando ‘Video Upload’ para ‘default’… al día
yarn run v1.22.19
$ /var/www/discourse/app/assets/javascripts/node_modules/.bin/ember build -prod
ADVERTENCIA: Node v18.16.1 no se ha probado con Ember CLI en tu plataforma. Recomendamos que uses la versión “Active LTS” más reciente de Node.js. Consulta ember-cli/docs/node-support.md at master · ember-cli/ember-cli · GitHub para más detalles.
Entorno: producción
limpiando…
info Visita yarn run | Yarn para documentación sobre este comando.

I, [2023-07-04T08:40:44.827572 #1] INFO – : Terminando procesos asíncronos
I, [2023-07-04T08:40:44.827621 #1] INFO – : Enviando INT a HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/13/bin/postmaster -D /etc/postgresql/13/main pid: 41
I, [2023-07-04T08:40:44.827734 #1] INFO – : Enviando TERM a exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 102
102:signal-handler (1688460044) Recibido SIGTERM programando apagado…
2023-07-04 08:40:44.827 UTC [41] LOG: recibida solicitud de apagado rápido
102:M 04 Jul 2023 08:40:44.856 # Usuario solicitó apagado…
102:M 04 Jul 2023 08:40:44.856 * Guardando la instantánea RDB final antes de salir.
2023-07-04 08:40:44.883 UTC [41] LOG: abortando cualquier transacción activa
2023-07-04 08:40:44.886 UTC [41] LOG: trabajador de fondo “logical replication launcher” (PID 50) salió con código de salida 1
2023-07-04 08:40:44.887 UTC [45] LOG: apagando
102:M 04 Jul 2023 08:40:44.978 * BD guardada en disco
102:M 04 Jul 2023 08:40:44.978 # Redis está listo para salir, adiós…
2023-07-04 08:40:45.023 UTC [41] LOG: sistema de base de datos apagado

FALLIDO

Pups::ExecError: cd /var/www/discourse && su discourse -c ‘bundle exec rake themes:update assets:precompile’ falló con retorno #<Process::Status: pid 2320 exit 1>
Ubicación del fallo: /usr/local/lib/ruby/gems/3.2.0/gems/pups-1.1.1/lib/pups/exec_command.rb:117:in `spawn’
exec falló con los parámetros {“cd”=>“$home”, “hook”=>“assets_precompile”, “cmd”=>[“su discourse -c ‘bundle exec rake themes:update assets:precompile’”]}
bootstrap falló con código de salida 1
** FALLO EN EL BOOTSTRAP ** por favor desplázate hacia arriba y busca mensajes de error anteriores, puede haber más de uno.
./discourse-doctor puede ayudar a diagnosticar el problema.
64eb105c2de1517c880ea75102bf870c657542c35141dbec0fca357d33911198
==================== FIN DEL REGISTRO DE RECONSTRUCCIÓN ====================
Error al reconstruir la aplicación.

Comprobando tu nombre de dominio . . .

La conexión a redacted se realizó correctamente.
Probablemente deberías eliminar cualquier plugin no estándar y reconstruir.
Intentando reiniciar el contenedor existente. . .
Arquitectura x86_64 detectada.

iniciando contenedor existente

  • /usr/bin/docker start app
    Respuesta de error del demonio: el controlador falló al programar la conectividad externa en el extremo app (dc0e7be2e9a1b8644d73adf1e327236bdb49650ec05388fa81eb665e1ac1316f): Error al iniciar el proxy de userland: listen tcp 0.0.0.0:443: listen: dirección ya en uso
    Error: no se pudo iniciar los contenedores: app
    Error al reiniciar el contenedor.

==================== PLUGINS ====================
- git clone GitHub - discourse/docker_manager: Plugin for use with discourse docker image · GitHub

No se detectaron plugins no oficiales.

Consulta discourse/lib/plugin/metadata.rb at main · discourse/discourse · GitHub para la lista oficial.

========================================

Versión de Discourse en redacted: NO ENCONTRADA
Versión de Discourse en localhost: NO ENCONTRADA

==================== INFORMACIÓN DE MEMORIA ====================
RAM (MB): 3084

          total        usado        libre      compartido  buff/cache   disponible

Mem: 3012 416 1648 6 947 2401
Swap: 511 117 394

==================== VERIFICACIÓN DE ESPACIO EN DISCO ====================
---------- Espacio en disco del SO ----------
Sistema de archivos Tamaño Usado Disp Uso% Montado en
/dev/vda1 26G 20G 5.1G 80% /

==================== INFORMACIÓN DEL DISCO ====================
Disco /dev/vda: 26 GiB, 27917287424 bytes, 54525952 sectores
Unidades: sectores de 1 * 512 = 512 bytes
Tamaño de sector (lógico/físico): 512 bytes / 512 bytes
Tamaño de E/S (mínimo/óptimo): 512 bytes / 512 bytes
Tipo de etiqueta de disco: dos
Identificador de disco: 0xf849ba6e

Dispositivo Inicio Inicio Fin Sectores Tamaño Id Tipo
/dev/vda1 2048 54525951 54523904 26G 83 Linux

==================== FIN DE LA INFORMACIÓN DEL DISCO ====================

==================== PRUEBA DE CORREO ====================
Para una prueba robusta, obtén una dirección de http://www.mail-tester.com/
O simplemente envíate un mensaje de prueba.
¿Dirección de correo para la prueba de correo? (‘n’ para omitir) [redacted]: Enviando correo a redacted. . .
Respuesta de error del demonio: El contenedor 91601890406d42c06076f4468dfcc196af018179f6bc970a6983feb296ef00c5 no se está ejecutando

Reemplazando: SMTP_PASSWORD
Reemplazando: LETSENCRYPT_ACCOUNT_EMAIL
Reemplazando: DEVELOPER_EMAILS
Reemplazando: DISCOURSE_DB_PASSWORD
Reemplazando: Enviando correo a

==================== ¡HECHO! ====================


[quote="Jay Pfaffman, post:3, topic:270491, username:pfaffman"]
Quizás ese sea un error en tu tema.
[/quote]

Solo hay el tema predeterminado (creo, tiene un nombre extraño "Migrated from Site Text" y fue creado por `system`) con 3 componentes adicionales (`Disco TOC`, `Sick - Gallery Component` y `Video Upload`). Intenté deshabilitar estos componentes y reconstruir, pero obtuve el mismo error.

[quote="Jay Pfaffman, post:3, topic:270491, username:pfaffman"]
¿Ejecutar

`./launcher start app`

hará que tu sitio funcione?
[/quote]

Antes de mi cambio en `base_store.rb`, sí iniciaba la aplicación, pero acceder al foro desde un navegador resultaba en el error Oops 500, con el error de sintaxis en el registro.

Con el cambio en `base_store.rb`, el foro parece funcionar bien. Simplemente no puedo reconstruirlo. El panel de control dice que estoy en la última versión: 3.0.4 (cec7c05dae). Y cuando hago clic en el enlace de actualización, dice que debo actualizar usando ssh. Mi `/var/discourse` está en el commit `984d5495edfa8af028ab6809407af817d555125c`, que parece ser el más reciente, así que probablemente solo dice eso porque la aplicación no se ha reconstruido en este commit.

Por curiosidad, ¿cómo estás instalando los plugins a través de la interfaz del navegador?

1 me gusta

Creo que confundí los plugins y los componentes del tema. Solo los componentes del tema se instalaron a través de la interfaz del navegador.

2 Me gusta

Ah, esto hace que las cosas sean un poco diferentes de lo habitual, creo, ya que casi todas las instalaciones ejecutan tests-passed. Ver ¿Por qué Discourse siempre instala las versiones “beta” por defecto?

2 Me gusta

Gracias por informar del problema @sigmike. El problema de la versión de Ruby se solucionará con una reconstrucción, por lo que nuestro objetivo principal aquí debería ser que la reconstrucción se complete.

Pude reproducir el Build Error en una instalación nueva de la rama estable. Parece que yarn (el gestor de paquetes de JS que usamos) no está degradando limpiamente el espacio de trabajo desde los paquetes ‘tests-passed’ preinstalados a las versiones requeridas por la rama estable.

A medio plazo, nuestro objetivo es dejar de usar yarn como gestor de paquetes. Así que, por ahora, he añadido una solución alternativa al proceso de compilación que restablecerá el directorio node_modules al hacer una reconstrucción para instalaciones que no sean tests-passed. Si vuelves a intentar reconstruir, las cosas deberían funcionar mucho mejor.

¡Dinos cómo va!

9 Me gusta

Eso solucionó la reconstrucción, gracias.

Parece que la versión test-passed está más probada en batalla y las reconstrucciones también serían más rápidas, así que probablemente cambiaré a esa. Sin embargo, el sitio ha estado funcionando en stable desde 2016 sin problemas.

5 Me gusta

En mi opinión, con una versión estable debería ser posible mantener la misma imagen base durante todo el ciclo de lanzamiento; esta es la primera vez que se hace imposible (debido a esa única línea que requiere Ruby 3.2).

1 me gusta

Lamentablemente, no podemos mantener la imagen base estática durante 6 a 12 meses. Los paquetes instalados en la imagen de Docker reciben actualizaciones de seguridad y debemos implementarlas para las personas en la rama estable.

En este caso, tuvimos la opción de crear y mantener una imagen completamente separada de ‘Ruby 3.1’ para la rama estable, o hacer backporting de pequeños ajustes para que la rama estable se ejecutara en la última imagen. Elegimos lo último porque requería menos trabajo y menos riesgo. Significa que todos están utilizando la misma imagen que probamos e implementamos rigurosamente en nuestro hosting.

6 Me gusta