search for: meta_work

...leases/20071224050255/vendor/plugins/backgroundrb/lib/../framework/nbio.rb:55:in `dump_object'' /var/www/apps/rpg/releases/20071224050255/vendor/plugins/backgroundrb/framework/worker.rb:32:in `send_data'' /var/www/apps/rpg/releases/20071224050255/vendor/plugins/backgroundrb/server/meta_worker.rb:291:in `send_response'' /var/www/apps/rpg/releases/20071224050255/vendor/plugins/backgroundrb/server/meta_worker.rb:224:in `process_request'' /var/www/apps/rpg/releases/20071224050255/vendor/plugins/backgroundrb/server/meta_worker.rb:202:in `receive_data'' /var/www/a...

I propose changing meta_worker.rb line 240 from: result = "dummy_result" unless result to result = "dummy_result" unless defined?(result) If my worker is returning false, I get "dummy_result" instead. Thanks! Norman

...lains: brb-test/vendor/plugins/backgroundrb/server/cron_trigger.rb:161:in `local'': argument out of range (ArgumentError) from brb-test/vendor/plugins/backgroundrb/server/cron_trigger.rb:161:in `fire_time_after'' from brb-test/vendor/plugins/backgroundrb/server/meta_worker.rb:266:in `new_load_schedule'' from brb-test/vendor/plugins/backgroundrb/server/meta_worker.rb:258:in `each'' from brb-test/vendor/plugins/backgroundrb/server/meta_worker.rb:258:in `new_load_schedule'' from brb-test/vendor/plugins/backgroundrb/se...

...est_worker.rb:15:in `save_image'': You have a nil object when you didn''t expect it! (NoMethodError) You might have expected an instance of ActiveRecord::Base. The error occurred while evaluating nil.[] from /Users/BBryant/Sites/ date_site/trunk/vendor/plugins/backgroundrb/server/meta_worker.rb: 223:in `send'' from /Users/BBryant/Sites/date_site/trunk/vendor/plugins/backgroundrb/ server/meta_worker.rb:223:in `process_request'' from /Users/BBryant/Sites/date_site/trunk/vendor/plugins/backgroundrb/ server/meta_worker.rb:207:in `receive_data'' from /Users/B...

I tried to upgrade my existing application to RC2 last night. Like many, I use this mostly for running scheduled tasks. For the moment, I''ve abandoned the effort, but am looking forward to being able to use this. Feedback below: First, the reason I was looking forward to this upgrade was to use the threaded scheduler. I have an application with long-running tasks. I found that

...at script/backgroudrb requires config/environment which causes the backgroundrb server as well as the log worker to ''bloat'' to 35MB each. I am kind of sensitive to memory issues, so I patched the code and essentially moved the require of environment from script/backgroundrb to the meta_worker. Everything seems good and now both backgroundrb server and log worker hang around 12MB. Is there a reason why script/backgroundrb loads the environment? I suppose it makes spawning rail workers faster? Anyways, if anyone is interested, I can post my simple patch. Paul

...:160:in `local'': argument out o f range (ArgumentError) from /home/mengkuan/apps/testrailsapp/current/vendor/plugins/ backgroundrb/server/cron_trigger.rb:160:in `fire_time _after'' from /home/mengkuan/apps/testrailsapp/current/vendor/plugins/ backgroundrb/server/meta_worker.rb:266:in `new_load_s chedule'' from /home/mengkuan/apps/testrailsapp/current/vendor/plugins/ backgroundrb/server/meta_worker.rb:258:in `each'' from /home/mengkuan/apps/testrailsapp/current/vendor/plugins/ backgroundrb/server/meta_worker.rb:258:in `new_load_s c...

...s/config/../vendor/plugins/ batched_sql_fu/lib/batched_sql_fu/active_record.rb:8:in `insert_by_batch'' from /Users/jdonalds/Sites/3dial_ads/lib/workers/ process_list_worker.rb:249:in `process_leads'' from /Users/jdonalds/Sites/3dial_ads/vendor/plugins/backgroundrb/ server/lib/meta_worker.rb:235:in `send'' from /Users/jdonalds/Sites/3dial_ads/vendor/plugins/backgroundrb/ server/lib/meta_worker.rb:235:in `process_request'' from /Users/jdonalds/Sites/3dial_ads/vendor/plugins/backgroundrb/ server/lib/meta_worker.rb:219:in `receive_data'' from /Library/Rub...

...n/trunk/vendor/plugins/backgroundrb/server/lib/cron_trigger.rb:21:in `loop'' from /Users/pkmiec/src/propertyadmin/trunk/vendor/plugins/backgroundrb/server/lib/cron_trigger.rb:21:in `fire_after_time'' from /Users/pkmiec/src/propertyadmin/trunk/vendor/plugins/backgroundrb/server/lib/meta_worker.rb:336:in `check_for_timer_events'' from /Users/pkmiec/src/propertyadmin/trunk/vendor/plugins/backgroundrb/server/lib/meta_worker.rb:325:in `each'' from /Users/pkmiec/src/propertyadmin/trunk/vendor/plugins/backgroundrb/server/lib/meta_worker.rb:325:in `check_for_timer_events'...

...r I get whenever the register_status method is encountered: ...lib/workers/session_worker.rb:10:in `create'': undefined method `register_status'' for #<SessionWorker:0xb6e7d52c> (NoMethodError) from /home/rut216/dev/illinicourses/vendor/plugins/backgroundrb/server/lib/meta_worker.rb:129:in `worker_init'' from /var/lib/gems/1.8/gems/packet-0.1.14/bin/../lib/packet/packet_worker.rb:19:in `start_worker'' from /var/lib/gems/1.8/gems/packet-0.1.14/bin/packet_worker_runner:33:in `load_worker'' from /var/lib/gems/1.8/gems/packet-0....

Hi there I have recently upgraded to v1.0.1 and I''ve noticed an issue which I don''t believe was present in the 0.2 release. In my worker class I am logging errors as follows: logger.error "the error message" However, this now causes an exception to be thrown in the new version: undefined method `error'' for

...ype=>"past_perfect4"} Arity of method is -1 That seems to be the end of the road for the worker. It just stalls there from what I can tell. What does Arity mean? Any clues? I suspect it''s something small I''m missing. Also, I replaced this on line 210 of server/meta_worker.rb: logger.info "#{user_input[:worker_method]} #{user_input[:data]}" with this: logger.info "#{user_input[:worker_method]} #{user_input[:data].inspect}" for nicer debugging formatting. Seems like it might be a nice improvement. Cheers, Walter McGinnis...

...ule'' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_nbio.rb:72:in `dump_object'' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_worker.rb:31:in `send_data'' from /home/test/work/vendor/plugins/backgroundrb/server/lib/meta_worker.rb:284:in `register_status'' ... 9 levels... from /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_master.rb:20:in `run'' from /home/test/work/vendor/plugins/backgroundrb/server/lib/master_worker.rb:166:in `initialize'' from scrip...

I lost my "connection lost" error.. but now I''ve got a "Mysql::Error: MySQL server has gone away" error.. It comes from: /usr/lib/ruby/gems/1.8/gems/activerecord-1.15.6/lib/active_record/connection_adapters/abstract_adapter.rb:128:in ''log''. I''m not sure if Rails / BackgroundRb uses it .. but i''ve got the mysql (2.7) gem

...StatusChecker: processing domain webconsole 2008-01-16 16:10 StatusChecker: processing host host1 After 16:10 the worker seems to have disappeared. I found the following message in backgroundrb_debug.log: /home/webcon/apps/webconsole/releases/20080115103838/vendor/plugins/ backgroundrb/server/meta_worker.rb:329:in `check_for _timer_events'': undefined method `info'' for nil:NilClass (NoMethodError) from /home/webcon/apps/webconsole/releases/20080115103838/ vendor/plugins/backgroundrb/framework/core.rb:148:in ` start_reactor'' from /home/webcon/apps/webco...

I''m using a plugin which adds a method to ActiveRecord::Base http://similetimelinerailshelper.googlecode.com/svn/trunk/simile_timeline/ This adds an "acts_as" type declaration to the Models, via the file in vendor/plugins/simile_timeline/lib/simile_timeline.rb Rails is working with these declarations, and they are being used successfully in ''regular