-
Notifications
You must be signed in to change notification settings - Fork 954
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
DelayedJob cannot find a CarrierWave uploader class #1221
Comments
If you are trying to background an upload, you should never do that in any background job processor. |
Hi @albus522 , thank you for the quick reply. We are not trying to background an upload actually, we are emitting an EventBridge event (related to an organization being updated) in the background. This event has recently been updated to include a |
Serializing an unsaved record is not going to work the way you want. It will be loaded as a fresh copy from the database at a step after the error you are currently hitting. |
Hi, I'm not sure if this is the appropriate place to post this, but it seems like an issue. I am running into this error:
Job Delayed::PerformableMethod (id=3200623) (queue=default) FAILED permanently with Delayed::DeserializationError: Job failed to load: undefined class/module LogoUploader::WebVersionUploader.
I think this class is dynamically generated by CarrierWave using
const_set
, it seems like from here: https://github.com/carrierwaveuploader/carrierwave/blob/a5518d6ae6d2cd1dc12776fe76ac49b8ccf6d551/lib/carrierwave/uploader/versions.rb#L23 (we are using an older version, with slightly different name). Is there a way to autoload this constant so that DelayedJob can pick it up? I've triedrequire 'carrierwave'
andrequire 'carrierwave/versions'
inapplication.rb
, and it does not help. We are using DelayedJob 4.1.11. Please let me know if any other details would help with this, or is it a limitation of DelayedJob and dynamically generated classes/methods? I've noticed a similar error forattr_accessor
as well.The text was updated successfully, but these errors were encountered: