Open matthewbloch opened 2 years ago
I think this is a bug in ActiveSupport 7 https://github.com/rails/rails/issues/43851
It is a change in ActiveSupport 7 (I've seen it crop up in a couple different places already too), but apparently is by design per rails/rails#44450. The suggested fix is to add require "active_support"
(which sets up a bunch of autoloads) to somewhere in Xeroizer's loading sequence.
PRs welcome for this.
https://github.com/waynerobinson/xeroizer/blob/master/lib/xeroizer.rb is what is done now
I think that Xeroizer has forgotten to
require 'active_support/isolated_execution_state'
somewhere, which presumably gets done automatically in Rails. This is currently what happens when you try to require xeroizer outside of Rails:Obviously the workaround is just to
require 'active_support/isolated_execution_state'
beforerequire 'xeroizer'
.