-
Notifications
You must be signed in to change notification settings - Fork 21.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
uninitialized constant ActiveSupport::XmlMini::IsolatedExecutionState #43851
Comments
The fix would be either for rails to add |
I stumbled across this error when trying to do: require "active_record/base"
class StagedJob < ActiveRecord::Base
end This is a gem and not a Rails app, so I have to require Unfortunately this doesn't work and throws Anyway, I changed it to: require "active_record"
class StagedJob < ActiveRecord::Base
end and now it works properly 🎉 That's because Leaving this comment here, in case somebody finds it useful. |
I just stumbled against this error again while upgrading my app to rails 7 Failure/Error: require "active_support/testing/time_helpers"
NameError:
uninitialized constant ActiveSupport::XmlMini::IsolatedExecutionState
# /Users/dorianmariefr/.rvm/gems/ruby-3.0.3/gems/activesupport-7.0.0/lib/active_support/xml_mini.rb:184:in `current_thread_backend'
# /Users/dorianmariefr/.rvm/gems/ruby-3.0.3/gems/activesupport-7.0.0/lib/active_support/xml_mini.rb:103:in `backend='
# /Users/dorianmariefr/.rvm/gems/ruby-3.0.3/gems/activesupport-7.0.0/lib/active_support/xml_mini.rb:201:in `<module:ActiveSupport>'
# /Users/dorianmariefr/.rvm/gems/ruby-3.0.3/gems/activesupport-7.0.0/lib/active_support/xml_mini.rb:11:in `<top (required)>'
# /Users/dorianmariefr/.rvm/gems/ruby-3.0.3/gems/activesupport-7.0.0/lib/active_support/core_ext/array/conversions.rb:3:in `require'
# /Users/dorianmariefr/.rvm/gems/ruby-3.0.3/gems/activesupport-7.0.0/lib/active_support/core_ext/array/conversions.rb:3:in `<top (required)>'
# /Users/dorianmariefr/.rvm/gems/ruby-3.0.3/gems/activesupport-7.0.0/lib/active_support/duration.rb:3:in `require'
# /Users/dorianmariefr/.rvm/gems/ruby-3.0.3/gems/activesupport-7.0.0/lib/active_support/duration.rb:3:in `<top (required)>'
# /Users/dorianmariefr/.rvm/gems/ruby-3.0.3/gems/activesupport-7.0.0/lib/active_support/core_ext/time/calculations.rb:3:in `require'
# /Users/dorianmariefr/.rvm/gems/ruby-3.0.3/gems/activesupport-7.0.0/lib/active_support/core_ext/time/calculations.rb:3:in `<top (required)>'
# /Users/dorianmariefr/.rvm/gems/ruby-3.0.3/gems/activesupport-7.0.0/lib/active_support/testing/time_helpers.rb:4:in `require'
# /Users/dorianmariefr/.rvm/gems/ruby-3.0.3/gems/activesupport-7.0.0/lib/active_support/testing/time_helpers.rb:4:in `<top (required)>'
# ./spec/spec_helper.rb:6:in `require'
# ./spec/spec_helper.rb:6:in `<top (required)>' The fix was to do: require "active_support"
require "active_support/testing/time_helpers" |
Same with |
…State It was breaking specs and sample app from running. based on solution here: rails/rails#43851 (comment)
This has changed in later releases of ActiveSupport, see this Issue: rails/rails#43851
This has changed in later releases of ActiveSupport, see this Issue: rails/rails#43851
This has changed in later releases of ActiveSupport, see this Issue: rails/rails#43851
When running the test suite with activesupport version 7, an unitialized constant error for `XmlMini::IsolatedExecutionState` is raised. As described here: - rails/rails#43851 - rails/rails#43852 The resolution for this is to first require `active_support` before requiring `core_ext/string` so that autoloading happens correctly.
When running the test suite with activesupport version 7, an unitialized constant error for `XmlMini::IsolatedExecutionState` is raised. As described here: - rails/rails#43851 - rails/rails#43852 The resolution for this is to first require `active_support` before requiring `core_ext/string` so that autoloading happens correctly.
…tate After the move to Rails 7, the following error was causing tests to fail: ``` uninitialized constant ActiveSupport::XmlMini::IsolatedExecutionState ``` The solution was to explicitly require `active_support` before requiring the Hash and Array core extensions. This is the suggested approach given in the [Active Support documentation][1], but presumably the previous combination of Ruby and Rails was more forgiving of its omittance. This change is based on the solution identified here: rails/rails#43851 (comment) [1]: https://guides.rubyonrails.org/active_support_core_extensions.html#stand-alone-active-support
…tate After the move to Rails 7, the following error was causing tests to fail: ``` uninitialized constant ActiveSupport::XmlMini::IsolatedExecutionState ``` The solution was to explicitly require `active_support` before requiring the Hash and Array core extensions. This is the suggested approach given in the [Active Support documentation][1], but presumably the previous combination of Ruby and Rails was more forgiving of its omittance. This change is based on the solution identified here: rails/rails#43851 (comment) [1]: https://guides.rubyonrails.org/active_support_core_extensions.html#stand-alone-active-support
…tate After the move to Rails 7, the following error was causing tests to fail: ``` uninitialized constant ActiveSupport::XmlMini::IsolatedExecutionState ``` The solution was to explicitly require `active_support` before requiring the Hash and Array core extensions. This is the suggested approach given in the [Active Support documentation][1], but presumably the previous combination of Ruby and Rails was more forgiving of its omittance. This change is based on the solution identified here: rails/rails#43851 (comment) [1]: https://guides.rubyonrails.org/active_support_core_extensions.html#stand-alone-active-support
…tate After the move to Rails 7, the following error was causing tests to fail: ``` uninitialized constant ActiveSupport::XmlMini::IsolatedExecutionState ``` The solution was to explicitly require `active_support` before requiring the Hash and Array core extensions. This is the suggested approach given in the [Active Support documentation][1], but presumably the previous combination of Ruby and Rails was more forgiving of its omittance. This change is based on the solution identified here: rails/rails#43851 (comment) [1]: https://guides.rubyonrails.org/active_support_core_extensions.html#stand-alone-active-support
require in which file please ? |
@jaswinderahuja wherever you are requiring active support time helpers, you need to require active support first |
Steps to reproduce
It seems like there is a bug in cocoapods but seems related to the 7.0.0rc1 version of rails, so posting here and there in case
Expected behavior
Upgrades pods, works fine
Actual behavior
An error
System configuration
Rails version:
Ruby version:
The text was updated successfully, but these errors were encountered: