-
Notifications
You must be signed in to change notification settings - Fork 65
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
Delayed::DeserializationError #50
Comments
I have the same issue periodically. Running 'rake jobs:clear' works for me to clear it out... rake jobs:clear # Clear the delayed_job queue. |
Could be something to do with this comment collectiveidea/delayed_job#183 (comment) --> basically if delayed job tries to retrieve a job referencing an AR object and that object has been deleted, you don't get a ActiveRecord::RecordNotFound but a Delayed::DeserizalisationError --> https://github.com/collectiveidea/delayed_job/blob/b4a80598faf9e6399e2208c26a50b5c9ffa45afd/lib/delayed/serialization/active_record.rb (the head at time of writing) |
I'm experiencing simular issue: delayed_job's last_error contains: |
I use DJ to handle a lot of my after_creates and was running into similar issues. I wasn't able to find a way around it using the delay.do_the_job method, but am able to keep it from happening by passing the object id and doing an explicit AR find_by_id. I created a generic AfterCreateJob class that I can use to handle all of my delayed after_create needs Maybe there's a better way to handle it, but here's what I'm doing. class SomeModel < ActiveRecord::Base private def job_to_run def another_job_to_run end class AfterCreateJob < Struct.new(:id, :klass) def logger end |
lazy "fix":
|
@ypadlyak have you solved that issue? |
The Project seems to be down now. We have switched to Gitlab a long time ago |
I get the following error when I try to build a project after deleting failed or hung builds. Not exactly sure what's happening here, but it seems like something is getting corrupted in DelayedJob. It would be nice to have some sort of "big red button" clear the job queue feature.
The text was updated successfully, but these errors were encountered: