search for: mengkuan

...chedule a worker to run during the midnight hour like this: :schedules: :collector: :process_something: :trigger_args: 30 * 0 * * 2,3,4,5,6 When I try to start backgroundrb, the "collector" worker failed to start up and I find this in backgroundrb_server.log: /home/mengkuan/apps/testrailsapp/current/vendor/plugins/backgroundrb/ server/cron_trigger.rb: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...

...ubuntu dapper - ruby 1.8.4 - backgroundrb 0.2.1 as well as mac osx 10.4.9 - ruby 1.8.5 - backgroundrb 0.2.1 but no luck. Does thread pool work for anyone properly? Or do you use some other methods like implementing your own queue system? Appreciate any hints. Thanks! cheers, mengkuan

...ever to use sleep() in workers. However, currently I have a need for a worker to issue a command to an external host and then keep checking that external host for a status change. Other than sleep, what else can be used to make a worker wait some time (say 1 second) between checks? cheers, mengkuan

...I''m not sure where the problem lies, but after looking at the changelogs for 0.6.6 and 0.6.7, it seems that keep-alives might be the culprit here. In any case, I''m back to using 0.6.5 and the app is working fine. Hopefully this helps somebody who is using mechanize. cheers, mengkuan

I''m having some problems with ActionMailer and I''m hoping that someone can help. I''ve followed the tutorial on "How To Send Emails With Action Mailer" <URL: http://wiki.rubyonrails.com/rails/show/HowToSendEmailsWithActionMailer >, I''ve generated a mailer -- "notifier.rb" -- and I''ve added the following method to the

Hi All I just finished writing up a tutorial relating my experience developing a system to edit line-items ''in-line'' in my Rails application using XMLHttpRequest. I thought this might be of interest to some readers of this list... Check it out at http://hieraki.goodlad.ca/read/book/1 Thanks! Dave -- Dave Goodlad dgoodlad-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org or

...(23325) /usr/lib/ruby/gems/1.8/gems/slave-1.2.0/lib/ slave.rb:435:in `initialize'' If I can get autostart to work, I will not need to use the scheduling mechanism. Any hints? If autostart is not available, how can one start a worker when the backgroundrb daemon is started? cheers, mengkuan

Hello all, If I run this script, and observe the output, the results are not there at all (try to do the same in the browser). Any suggestions? require ''rubygems'' require ''mechanize'' agent = WWW::Mechanize.new agent.user_agent_alias = ''Mac Safari'' page =

Hello all, I have tried to post this yesterday, but noticed I was actually not subscribed yet... Well, here we go again: If I run this script, and observe the output, the results are not there at all (try to do the same in the browser). Any suggestions? require ''rubygems'' require ''mechanize'' agent = WWW::Mechanize.new agent.user_agent_alias =

...`initialize'' from script/backgroundrb:41:in `new'' from script/backgroundrb:41 The code for this worker can be found here: https://svn.sxven.com/webconsole/trunk/lib/workers/status_checker.rb Any pointers on how to debug this is much appreciated. cheers, mengkuan

Hi everyone, We had a really successful meeting tonight in Atlanta. The topic was an introduction to Ruby on Rails and our attendance was 30 people, which is over double of what we normally get. (Our attendance has dropped since moving the venue about 25 miles north of the city. The majority of the group stayed well past two hours, at which point we took a break. The entire presentation and

I need to run the same worker''s method twice per day with different arguments. Unfortunately, only the second entry in the schedule is firing. I created an experimental worker to verify this: Worker: class ExperimentWorker < BackgrounDRb::MetaWorker set_worker_name :experiment_worker def create(args = nil) # this method is called, when worker is loaded for the first time

Hi, I found the following in the logs of a server that crashed: Mar 19 14:09:28 sc4 kernel: Assertion failure in ext3_free_blocks() at balloc.c line 358: "bh->b_committed_data != NULL" Mar 19 14:09:28 sc4 kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000000 Mar 19 14:09:28 sc4 kernel: current->tss.cr3 = 39b8b000, %%cr3 = 39b8b000 Mar 19 14:09:28