stack level too deep about resque-status HOT 6 CLOSED

The problem is actually that Resque.encode calls to_json and then Resque::Status#to_json calls Resque.encode so it becomes an infinite loop (when using the JSON gem). I'm working on a way to fix this. Thanks

from resque-status.

I have the same problem. I think it's because my deployment doesn't use yajl, just regular json. I have a fork that I mucked with to get around the problem. Not as elegant as your original code (I encapsulate a hash rather than inherit from it).

from resque-status.

Hey All,
Just pushed a new version last night that includes this commit:
http://github.com/quirkey/resque-status/commit/836fd7449aa75f478266bc6b4241e7af1095ccce

Which should fix any issues with the JSON gem.

from resque-status.

That's weird. I'm using exactly this commit and i still have "stack level too deep" errors.

from resque-status.

My trace ... http://gist.github.com/396893

from resque-status.

Wow. I fixed the problem. It's a problem with Vlad.
http://stackoverflow.com/questions/3105384/why-im-getting-stack-level-too-deep-while-triggering-a-job-using-resque-status/3216054#3216054

from resque-status.