search for: lapier

I''m working on upgrading my app to the latest version of backgroundrb. Everything went find until I tried to execute my tasks. Here is my simple worker for testing: class MscWorker < BackgrounDRb::MetaWorker set_worker_name :msc_worker def create(args = nil) # this method is called, when worker is loaded for the first time end # Send a message to everyone def

Everything works fine on my development box (Ubuntu 7.10, Ruby 1.8.6) but on my server (Fedora Core 6, Ruby 1.8.5) when I run script/backgroundrb start, the process fails to start. This is with Rails 2.0.2 frozen in the app, and I have the most recent version of the plugin (r297). Is Ruby 1.8.6 a requirement for backgroundrb now? I can''t figure any other reason it would fail...

I''m trying to run a single worker that could perform a periodic task for a given user. >From a controller, I imagine something like: def start_job MiddleMan.ask_work(:worker => :foo_worker, :worker_method => :perform_task, :data => { :user_id = current_user.id }) end def check_job @status = MiddleMan.ask_status(:worker => :foo_worker)[current_user.id] end

I get this error periodically in backgroundrb.log, but only on my production box (the one running ruby 1.8.5) - my dev box doesn''t get this error. As far as I can tell, everything is working ok, despite the error (I don''t really know how to determine if the jobs are getting threaded successfully, but they are running, that I am sure of). Here''s the dump: no

After some initial stumblings, I think I''ve got the hang of backgroundrb. It''s great! I''d been thinking for many many months how cool something like this would be! I''m trying to make a "job queue". That is, a pool of worker threads monitor a queue. When a job appears, one of the workers grabs it and executes the task. When complete, the worker

Hi there I''m using the latest release (r300) and ''script/backgroundrb start'' works perfectly when executed on the server, but when put inside a Rake task, it doesn''t launch the worker processes. The Rake task is as follows: task :start_backgroundrb do run "cd #{current_path} && ./script/backgroundrb start" end When I run this task, the

When using the provided bdrb_test_helper, I was getting some undefined methods (register_status, thread_pool, etc) in unit tests. The README says to go ahead and stub out methods that need it, and send the patch to the list, so here it is (attached). Also, the MetaWorker initialize method was written as "initializes", causing the @logger never to be set, causing undefined method errors

I was using an older version of backgroundrb and today I started to play with the most recent release. First up, I''d like to say, thanks so much for this library and thanks for making it more stable. From the looks of things, I think it''s going to be easier to use now than it was several months ago when I first started using it. I''d like to make sure I''m using

We''ve all seen the job listings. We know what they''re looking for. Rockstars. Code Monkeys. Rails Ninjas. And you''re left thinking, "But I''m just a programmer." Well, not anymore. Today, you become a Rails Kung-Fu Master! "Not me," you say. "I''ve already tried using all the acts_as_something plugins and all the something_fu