Active Support Logger

Aperta
#74 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
30/100
Tipo di issue
Bug
Chiarezza
Da chiarire
Stato di attività
Ferma
Stack tecnologico
docker, rails, ruby
Ambito
devops

Direzione di ricerca

Inizia da doc/setup.md e riproduci il malfunzionamento in “Start Development Containers” usando docker compose up. Leggi il traceback di ActiveSupport in logger_thread_safe_level.rb e l’output circostante dell’avvio di Rails; il lavoro è completato quando i container di sviluppo si avviano senza il Logger NameError segnalato né terminare.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug
Aktuelles Verhalten

I worked through docker manual step by step. When executing docker compose up I get these errors:

webpack-1      | /opt/bundle/ruby/3.2.0/gems/activesupport-7.0.8.6/lib/active_support/logger_thread_safe_level.rb:12:in `<module:LoggerThreadSafeLevel>': uninitialized constant ActiveSupport::LoggerThreadSafeLevel::Logger (NameError)
webpack-1      |
webpack-1      |     Logger::Severity.constants.each do |severity|
webpack-1      |           ^^^^^^^^^^
webpack-1      | 	from /opt/bundle/ruby/3.2.0/gems/activesupport-7.0.8.6/lib/active_support/logger_thread_safe_level.rb:9:in `<module:ActiveSupport>'
webpack-1      | 	from /opt/bundle/ruby/3.2.0/gems/activesupport-7.0.8.6/lib/active_support/logger_thread_safe_level.rb:8:in `<main>'
webpack-1      | 	from <internal:/usr/local/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:38:in `require'
webpack-1      | 	from <internal:/usr/local/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:38:in `require'
webpack-1      | 	from /opt/bundle/ruby/3.2.0/gems/bootsnap-1.18.4/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require'
webpack-1      | 	from /opt/bundle/ruby/3.2.0/gems/activesupport-7.0.8.6/lib/active_support/logger_silence.rb:5:in `<main>'
webpack-1      | 	from <internal:/usr/local/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:38:in `require'
webpack-1      | 	from <internal:/usr/local/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:38:in `require'
webpack-1      | 	from /opt/bundle/ruby/3.2.0/gems/bootsnap-1.18.4/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require'
webpack-1      | 	from /opt/bundle/ruby/3.2.0/gems/activesupport-7.0.8.6/lib/active_support/logger.rb:3:in `<main>'
webpack-1      | 	from <internal:/usr/local/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:38:in `require'
webpack-1      | 	from <internal:/usr/local/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:38:in `require'
webpack-1      | 	from /opt/bundle/ruby/3.2.0/gems/bootsnap-1.18.4/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require'
webpack-1      | 	from /opt/bundle/ruby/3.2.0/gems/activesupport-7.0.8.6/lib/active_support.rb:29:in `<main>'
webpack-1      | 	from <internal:/usr/local/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:38:in `require'
webpack-1      | 	from <internal:/usr/local/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:38:in `require'
webpack-1      | 	from /opt/bundle/ruby/3.2.0/gems/bootsnap-1.18.4/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require'
webpack-1      | 	from /opt/bundle/ruby/3.2.0/gems/railties-7.0.8.6/lib/rails/command.rb:3:in `<main>'
webpack-1      | 	from <internal:/usr/local/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:38:in `require'
webpack-1      | 	from <internal:/usr/local/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:38:in `require'
webpack-1      | 	from /opt/bundle/ruby/3.2.0/gems/bootsnap-1.18.4/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require'
webpack-1      | 	from /opt/bundle/ruby/3.2.0/gems/railties-7.0.8.6/lib/rails/commands.rb:3:in `<main>'
webpack-1      | 	from <internal:/usr/local/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:38:in `require'
webpack-1      | 	from <internal:/usr/local/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:38:in `require'
webpack-1      | 	from /opt/bundle/ruby/3.2.0/gems/bootsnap-1.18.4/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require'
webpack-1      | 	from bin/rails:4:in `<main>'
Gewünschtes Verhalten

No errors, or at least no exits :)

Schritte zu reproduzieren

docker manual until Start Development Containers

Wann ist der Fehler aufgetreten?

No response

hitobito version

No response

Organisation

No response

Screenshots, weiterer Kontext

No response

ToDos

No response

Lingua principale
Shell
Stelle
23
Fork
18
Merge medio
1h 28m
PR unite (30g)
1

Preparare l'ambiente

  • Include un Dockerfile o un file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di hitobito/development

Tutte le issue di hitobito/development

Issue simili

Altre issue su Shell/Bash

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.