similar to: [PATCH] Unit Testing Rails Workers - It works!

Hey guys, I just opened up my first installation of BackgrounDRb and so far I love it. I''ll have to share this plugin at my next Ruby Brigade meeting! I have one question though: Is there a way that I can run the BackgrounDRb server in a "test" mode that will reload my changes without having to restart every time? (Similar to how mongrel does this with my

> Chris T wrote: > > Not sure this is known behaviour but it seems that if want to set > the > > environment to, for example, test, and you want to use Active > Record you > > have to both explicitly set the RAILS_ENV and the BackgrounDRb > environment. > > I ran into essentially the same problem (needing to run BRB in the > test > environment so

Hey Greg- Yes I am sorry, the new architecture uses fork and named pipes and a bunch of unix stuff to do its magick. Now you may be able to port it to qwork on windows, but I don''t think it is possible :( I''m really sorry about this but I need this thing to be as robust and solid as it can be and in the end windows isn''t compatible. Now you may be able to

Sorry for attaching patches in emails to the mailing list, but I''m still unable to login to Devjavu for Backgroundrb (I''m able to login just fine for Merb''s Devjavu and submitted a ticket successfully). Anyway, I encountered a bug when trying to #ask_status of a worker before it''s run (or rather, before its result_hash has been set to something). Not sure why

Ok two things that bug me 1) http://backgroundrb.devjavu.com/projects/backgroundrb/ticket/48 i thought i''ll just post ticket link - but well - it''s strange 2) when i switch base class from RailsBase to Base i can''t access MiddleMan - i get error NameError: uninitialized constant MiddleMan from (drbunix:///tmp/backgroundrbunix_localhost_2999)

Hi, I''m using backgroundrb but I have 2 problems with it. First is when I launch a thread Toto from the do_work method. Toto can''t access to a class variable defined before... (undefined method `+'' for nil:NilClass) I suspect that thread is launched when backgroundrb start but the worker not .. My code is : class MonWorker < BackgrounDRb::Worker::RailsBase

It''s that time again friends. skaar has been at it again and has greatly improved the stability of the new system. And Ara Howard has helped a ton by working with us on the slave library to iron out the wrinkles./ The results is a lot nicer backgroundrb for everyone. I have to say another huge thanks to skaar. He has singlehandedly wrote almost all of this new version and many

I can''t get to the code anymore. Devjavu''s svn is asking for a username and password. http://svn.devjavu.com/backgroundrb/ Authorization Required This server could not verify that you are authorized to access the document requested. Either you supplied the wrong credentials (e.g., bad password), or your browser doesn''t understand how to supply the credentials

Hi Folks, I am glad to announce a 1.0.1 release of BackgrounDRb library. It has numerous fixes and some nice feature updates, so please upgrade. Code: http://svn.devjavu.com/backgroundrb/tags/release-1.0.1/ Updates and Fixes: * Fixed issue with Mysql Lost connections * Message debugging can be disabled now with ''debug_log'' option in configuration file( :debug_log: false)

Hi Folks, BackgrounDRb is a Ruby job server and scheduler. Its main intent is to be used with Ruby on Rails applications for offloading long-running tasks. Since a Rails application blocks while serving a request it is best to move long-running tasks off into a background process that is divorced from http request/response cycle. This new release of BackgrounDRb is also modular and can be used

Hello Folks- I am really happy to announce the release of BackgrounDRb 0.2.0 . This is a complete rewrite and re-architecture of this codebase. I want to thank skaar for all of his hard work. I put out a call for help with the new architecture and skaar stepped up bigtime. I had already written the new scheduler and cron compatible syntax and moved to multi process architecture. But he

Hi devs, I was trying to open a new ticket with a minor doc patch at the BackgroundDrb Trac (http://backgroundrb.devjavu.com/) and it seems like only admins have permission to do so. Is this intended? I read in the readme that patches should be mailed to this list, but I much prefer to use Trac since there''s already one set up. Any reason Trac is not open to registered Devjavu users?

Hello, I''ve been trying to get the latest copy of BackgrounDRB as per the documentation here http://backgroundrb.rubyforge.org/. However, whenever I try to access http://svn.devjavu.com/backgroundrb/tags/release-0.2.1 I keep an authentication prompt and if I leave it blank I am declined access. Is there somewhere else to get the code or am I doing something wrong? Thanks, -carl --

After upgrading to backgroundrb 0.2.x, Rails barfs lstat errors left and right when using the console or webrick or mongrel on win32. We run our site on a Linux server, so I''m not trying to get backgroundrb to work on a win32 machine. I just want to quietly stop loading itself if it detects that it''s on a win32 machine so that the rest of Rails can continue to load. Most of

Hi Folks, I am glad to announce 1.0 release of BackgrounDRb. This would be a major release since 0.2 release of BackgrounDRb. Here is a brief summary of changes: - BackgrounDRb is DRb no longer. It makes use of EventDriven network programming library packet ( http://packet.googlecode.com ). - Since we moved to packet, many nasty thread issues, result hash corruption issues are totally

Hi Folks, Thanks for your patience, new release of BackgrounDRb is available now. You can get it from here: http://svn.devjavu.com/backgroundrb/trunk/ Yes, older version is deprecated and not supported anymore. A brief list of changes since last release is: 1. Now, each worker has logger objects, which can be used to log stuff. 2. A worker can be started or scheduled dynamically. 3. Multiple

Hi everyone, I''m new to backgroundrb, and I''m trying to get started with a simple example, yet with no success. This is the code that I have in RAILS_ROOT/lib/workers/testing_worker.rb class TestingWorker < BackgrounDRb::Worker::RailsBase def do_work(args) # This method is called in it''s own new thread when you # call new worker. args is set

This has been asked before, never well attended perhaps. Any thoughts on testing your workers? Current implementation is broken. An empty test case like this: require File.dirname(__FILE__) + ''/../test_helper'' require "#{RAILS_ROOT}/lib/workers/market_summary_worker" require "#{RAILS_ROOT}/vendor/plugins/backgroundrb/lib/backgroundrb.rb" require

Hi Folks, Thank you for feedback and error reports. I have fixed most of the errors that were reported and were valid. I have also removed some cruft that was way too clunky. Here is a brief summary of changes : - Now, you don''t define method process_request method in your worker. Its no longer required. Whatever methods, you want to call from rails should be directly defined

Since this morning, the server at http://svn.devjavu.com/backgroundrb is requiring authorized access. Could you guys look into it? Thanks, Saimon -- Saimon Moore Freelance Web Developer (Available for hire - For details visit http://saimonmoore.net) Skype: saimonmoore Yahoo IM: saimonmoore Google IM: saimonmoore