Rails 2.3.3

This is the update statement where it records the error. I don't see
the stacktrace anywhere else.

UPDATE `delayed_jobs` SET `locked_at` = NULL, `run_at` = '2010-02-12
05:58:24', `last_error` = 'undefined method `peeps_count\' for
#<YAML::Object:0x206e6fc>\n/Users/brianburridge/InternetProjects/
peepnote/app/models/import_job.rb:15:in `perform\'\n/Users/
brianburridge/InternetProjects/peepnote/vendor/plugins/delayed_job/lib/
delayed/job.rb:217:in `invoke_job\'\n/Users/brianburridge/
InternetProjects/peepnote/vendor/plugins/delayed_job/lib/delayed/
job.rb:92:in `run_with_lock\'\n/Library/Ruby/Gems/1.8/gems/
activesupport-2.3.3/lib/active_support/core_ext/benchmark.rb:10:in
`realtime\'\n/Users/brianburridge/InternetProjects/peepnote/vendor/
plugins/delayed_job/lib/delayed/job.rb:91:in `run_with_lock\'\n/Users/
brianburridge/InternetProjects/peepnote/vendor/plugins/delayed_job/lib/
delayed/job.rb:155:in `reserve_and_run_one_job\'\n/Users/brianburridge/
InternetProjects/peepnote/vendor/plugins/delayed_job/lib/delayed/
job.rb:154:in `each\'\n/Users/brianburridge/InternetProjects/peepnote/
vendor/plugins/delayed_job/lib/delayed/job.rb:154:in
`reserve_and_run_one_job\'\n/Users/brianburridge/InternetProjects/
peepnote/vendor/plugins/delayed_job/lib/delayed/job.rb:201:in `work_off
\'\n/Users/brianburridge/InternetProjects/peepnote/vendor/plugins/
delayed_job/lib/delayed/job.rb:200:in `times\'\n/Users/brianburridge/
InternetProjects/peepnote/vendor/plugins/delayed_job/lib/delayed/
job.rb:200:in `work_off\'\n/Users/brianburridge/InternetProjects/
peepnote/vendor/plugins/delayed_job/lib/delayed/worker.rb:28:in `start
\'\n/Library/Ruby/Gems/1.8/gems/activesupport-2.3.3/lib/active_support/
core_ext/benchmark.rb:10:in `realtime\'\n/Users/brianburridge/
InternetProjects/peepnote/vendor/plugins/delayed_job/lib/delayed/
worker.rb:27:in `start\'\n/Users/brianburridge/InternetProjects/
peepnote/vendor/plugins/delayed_job/lib/delayed/worker.rb:24:in `loop
\'\n/Users/brianburridge/InternetProjects/peepnote/vendor/plugins/
delayed_job/lib/delayed/worker.rb:24:in `start\'\n(irb):1:in
`irb_binding\'\n/System/Library/Frameworks/Ruby.framework/Versions/1.8/
usr/lib/ruby/1.8/irb/workspace.rb:52:in `irb_binding\'\n/System/
Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/irb/
workspace.rb:52', `attempts` = 8, `updated_at` = '2010-02-12
05:18:18', `locked_by` = NULL WHERE `id` = 9

On Feb 12, 12:13 am, Pat Allan <[email protected]> wrote:
> What's the stacktrace of the error? What version of Rails are you using?
>
> --
> Pat
>
> On 12/02/2010, at 4:06 PM, Brian wrote:
>
> > Just tried that, but still getting the same error.
>
> > On Feb 11, 11:45 pm, Pat Allan <[email protected]> wrote:
> >> Can you grab the latest ts-delayed-delta (1.0.2), see if that helps?
>
> >> Cheers
>
> >> --
> >> Pat
>
> >> On 12/02/2010, at 3:33 PM, Brian wrote:
>
> >>> I upgraded as said above and now when my delayed job run it throws an
> >>> error when I try to access any of the attributes saved with the
> >>> object. I get this error:
>
> >>> ImportJob failed with NoMethodError: undefined method `peeps_count'
> >>> for #<YAML::Object:0x222dd80>. If I switch back to using the old
> >>> thinking sphinx plugin it works again. Has something changed about the
> >>> way objects are serialized into the delayed_jobs table?
>
> >>> Right now my delayed job class starts like this:
>
> >>> class ImportJob
> >>>  attr_accessor :current_user
>
> >>>  def initialize(current_user)
> >>>    self.current_user = current_user
> >>>  end
>
> >>> It's the current_user object that I need to retrieve attributes from
> >>> during delayed processing, and was able to until now.
>
> >>> When I look in the db, in the handler column I can see the serialized
> >>> object, as before, and the attributes in there that I need, but I get
> >>> that error above.
>
> >>> --
> >>> You received this message because you are subscribed to the Google Groups 
> >>> "Thinking Sphinx" group.
> >>> To post to this group, send email to [email protected].
> >>> To unsubscribe from this group, send email to 
> >>> [email protected].
> >>> For more options, visit this group 
> >>> athttp://groups.google.com/group/thinking-sphinx?hl=en.
>
> > --
> > You received this message because you are subscribed to the Google Groups 
> > "Thinking Sphinx" group.
> > To post to this group, send email to [email protected].
> > To unsubscribe from this group, send email to 
> > [email protected].
> > For more options, visit this group 
> > athttp://groups.google.com/group/thinking-sphinx?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Thinking Sphinx" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/thinking-sphinx?hl=en.

Reply via email to