resque

I'm having trouble calling methods from an included module inside a resque worker. In the example below, I keep getting undefined method errrors when I attempt to call the say method inside the worker (which is in the TestLib module). I've reduced the code down to bare basics to illustrate the issue: Controller (/app/controllers/test_controller.rb) class TestController < ApplicationController def testque Resque.enqueue( TestWorker, "HI" ) end end Library (/lib/test_lib.rb) module TestLib def say( word ) puts word end end Worker (/workers/test_worker.rb) require 'test_lib' class TestWorker

I'm trying to battle some race cases with my background task manager. Essentially, I have a Thing object (already exists) and assign it some properties, and then save it. After it is saved with the new properties, I queue it in Resque, passing in the ID. thing = Thing.find(1) puts thing.foo # outputs "old value" thing.foo = "new value" thing.save ThingProcessor.queue_job(thing.id) The background job will load the object from the database using Thing.find(thing_id) . The problem is that we've found Resque is so fast at picking up the job and loading the Thing object from the ID, that it loads a

I'm trying to send Devise emails through Resque. Regular emails are getting sent through Resque just fine. And Devise emails are sent just fine, but not Devise emails through Resque. I get "Could not find a valid mapping" which implies that my helper overrides aren't getting picked up. I'm following this http://shaker.4-dogs.biz/2011/08/06/using-resque-to-send-mail-for-devise/ The odd thing is that to debug it I'm using a local copy of Devise and adding breakpoints in 'initialize_from_record' in Devise, which gets hit when I just use Devise alone. But when I send the Devise emails through

I used resque-scheduler for delay jobs in previous code: Resque.enqueue_in(options[:delay].seconds, self, context) Now I want to include resque-status to do the job but have no idea how they can work together. The latest resque-status source code supports scheduler, as in the source code: https://github.com/quirkey/resque-status/blob/master/lib/resque/plugins/status.rb # Wrapper API to forward a Resque::Job creation API call into a Resque::Plugins::Status call. # This is needed to be used with resque scheduler # http://github.com/bvandenbos/resque-scheduler def scheduled(queue, klass, *args)

I want all the enqueue calls to default to a certain queue unless specified otherwise so it's DRY and easier to maintain. In order to specify a queue, the documentation said to define a variable @queue = X within the class. So, I tried doing the following and it didn't work, any ideas? class ResqueJob class << self; attr_accessor :queue end @queue = :app end class ChildJob < ResqueJob def self.perform end end Resque.enqueue(ChildJob) Resque::NoQueueError: Jobs must be placed onto a queue. from /Library/Ruby/Gems/1.8/gems/resque-1.10.0/lib/resque/job.rb:44:in `create' from /Library/Ruby/Gems/1

I have successfully run resque on heroku cedar stack and mount the interface on rails. when I start the worker, Everything works fine. The worker process the job. But When i kill the worker, Resque still think that the worker is available. When I start another worker, it then think there are 2 worker but in fact there is only one running. I also notice form here http://devcenter.heroku.com/articles/ps that heroku send SIGTERM when killing a worker and if that does not terminate then it send SIGKILL. here is my worker logs 2011-08-11T02:32:45+00:00 heroku[worker.1]: Starting process with