NameError: uninitialized constant in Sidekiq (in a web/puma this does not happen)

[kapso]

This may not be an exactly Sidekiq issue, but this issue only happens in a Sidekiq process, so wanted to bring it up here.

We are getting this issue in active_record/destroy_association_async_job.rb:20:in perform, so this code - https://github.com/rails/rails/blob/main/activerecord/lib/active_record/destroy_association_async_job.rb#L20C27-L20C44

NameError: uninitialized constant PublicProject (NameError)

      Object.const_get(camel_cased_word)
            ^^^^^^^^^^
Did you mean?  PublicSuffix
  from active_support/inflector/methods.rb:290:in `constantize'
  from active_support/core_ext/string/inflections.rb:74:in `constantize'
  from active_record/destroy_association_async_job.rb:20:in `perform'
  from active_job/execution.rb:68:in `block in ActiveJob::Execution#_perform_job'
  from active_support/callbacks.rb:120:in `block in ActiveSupport::Callbacks#run_callbacks'
  from i18n.rb:353:in `with_locale'
  from active_job/translation.rb:9:in `block (2 levels) in <module:Translation>'
  from active_support/callbacks.rb:129:in `instance_exec'
  ...

We do use this gem in the project - https://simonecarletti.com/code/publicsuffix-ruby/

class Project < ApplicationRecord
  has_many :public_projects, dependent: :destroy_async
end

I read somewhere that adding this in sidekiq.rb initializer may fix this issue. So the question is, is it safe to add this in Sidekiq?

Rails.application.config.after_initialize do
  Rails.autoloaders.main.eager_load
end

Versions:

• Rails 8.0.3
• Sidekiq v8.0.4 / Pro v8.0.1
• Ruby 3.4.4

[mperham]

I don’t know the issue. Rails autoloading is not something I can support very effectively as there’s a million ways you can configure your app into breaking it subtly.

I would advise against hacks like that initializer. Focus on figuring out the root cause, I don't know what side effects that snippet might have.

[kapso]

Sounds good, that makes sense.