Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Truncated YAML crashes the delayed_job daemon #12

Open
dball opened this Issue Oct 30, 2009 · 5 comments

Comments

Projects
None yet
6 participants

dball commented Oct 30, 2009

We were working with some beefy jobs that silently overflowed the default TEXT columns in mysql. The truncated YAML data were unable to be loaded, and were causing the daemon to crash. It looks like incomplete error handling in the job.deserialize method to me; the second YAML.load call doesn't have a rescue block, and the main rescue block for the method doesn't catch the YAML syntax error.

similar error...has anyone got solution ??

I've experienced the same thing! Also, using Class.delay.method(String), the string has some characters in it that cause deserialization to fail, thereby killing the whole thing.

Me too - Seems like YAML chokes on some input. Is there a way to safely encode the data before passing to delay?

enthooz commented Feb 28, 2013

When possible, it is more reliable to create a job using a unique identifier of a record, such as an ID, rather than the instance itself.

Pryrios commented Apr 4, 2013

Did anyone of you solved this issue?

I have a job on my table which won't be deleted as the YAML is truncated. ¿is it safe to delete if from the table?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment