Active Support Logger
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 30/100
Research direction
Start with doc/setup.md and reproduce the failure at “Start Development Containers” using docker compose up. Read the ActiveSupport logger_thread_safe_level.rb traceback and the surrounding Rails startup output; done means the development containers start without the reported Logger NameError or exiting.
Written by the indexing model from the issue text.
Description
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
- Dominant language
- Shell
- Stars
- 23
- Forks
- 18
- Avg merge
- 1h 28m
- Merged PRs (30d)
- 1
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from hitobito/development
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
hitobito/development#83 ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 48/100
hitobito/development#72 · 2 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
hitobito/development#48 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
hitobito/development#23 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
hitobito/development#15 ·
All issues in hitobito/development
Similar issues
-
bot-found documentation priority: P3
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
madenvel/KalinkaPlayer#602 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
huggingface/kernels#1006 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 94/100
Maintainers usually reply within 2 days
-
severity: low
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
luainkernel/lunatik#2594 ·
Maintainers usually reply within 1 day