导轨 6.1.7.10
红宝石2.6.6.
刚刚从 6.1.7.8 捆绑更新到 6.1.7.10 现在运行应用程序,我收到以下错误:
/home/cb/.gem/ruby/2.6.6/gems/activesupport-6.1.7.10/lib/active_support/logger_thread_safe_level.rb:16:in `module:LoggerThreadSafeLevel':未初始化的常量 ActiveSupport::LoggerThreadSafeLevel::Logger (NameError)
回溯显示:
...
14: from /home/cb/work/sb/config/environment.rb:2:in `<top (required)>'
13: from /home/cb/work/sb/config/environment.rb:2:in `require_relative'
12: from /home/cb/work/sb/config/application.rb:3:in `<top (required)>'
11: from /home/cb/work/sb/config/application.rb:3:in `require'
10: from /home/cb/.gem/ruby/2.6.6/gems/railties-6.1.7.10/lib/rails.rb:7:in `<top (required)>'
9: from /home/cb/.gem/ruby/2.6.6/gems/railties-6.1.7.10/lib/rails.rb:7:in `require'
8: from /home/cb/.gem/ruby/2.6.6/gems/activesupport-6.1.7.10/lib/active_support.rb:29:in `<top (required)>'
7: from /home/cb/.gem/ruby/2.6.6/gems/activesupport-6.1.7.10/lib/active_support.rb:29:in `require'
6: from /home/cb/.gem/ruby/2.6.6/gems/activesupport-6.1.7.10/lib/active_support/logger.rb:3:in `<top (required)>'
5: from /home/cb/.gem/ruby/2.6.6/gems/activesupport-6.1.7.10/lib/active_support/logger.rb:3:in `require'
4: from /home/cb/.gem/ruby/2.6.6/gems/activesupport-6.1.7.10/lib/active_support/logger_silence.rb:5:in `<top (required)>'
3: from /home/cb/.gem/ruby/2.6.6/gems/activesupport-6.1.7.10/lib/active_support/logger_silence.rb:5:in `require'
2: from /home/cb/.gem/ruby/2.6.6/gems/activesupport-6.1.7.10/lib/active_support/logger_thread_safe_level.rb:8:in `<top (required)>'
1: from /home/cb/.gem/ruby/2.6.6/gems/activesupport-6.1.7.10/lib/active_support/logger_thread_safe_level.rb:9:in `<module:ActiveSupport>'
/home/cb/.gem/ruby/2.6.6/gems/activesupport-6.1.7.10/lib/active_support/logger_thread_safe_level.rb:16:in `<module:LoggerThreadSafeLevel>': uninitialized constant ActiveSupport::LoggerThreadSafeLevel::Logger (NameError)
rails 控制台不受影响
无法找到应用程序中现在发生这种情况的原因
在我们的例子中,并发 ruby 版本已更新,它依赖于 activesupport gem。
concurrent-ruby 的 1.3.5 版本几个小时前刚刚发布,但我认为它有一个问题。
因此,我们在 gemfile 中将并发 ruby 的版本修复为 1.3.4,然后它再次开始工作。
希望这也能解决您的问题。