similar to: BackgrounDRb 1.0.1 release available now

Displaying 20 results from an estimated 1000 matches similar to: "BackgrounDRb 1.0.1 release available now"

2008 Jan 04
1
Updates and Fixes on Trunk
Hi, I am pushing some updates and fixes that addresses much of the issues that we talked about since last couple of days. 1. Use configuration option :debug_log: false to disable backgroundrb_debug.log. 2. As shown below, use lazy_load option to disable aggressive loading of models ( and somewhat stupid too). 3. MiddleMan.delete_worker(:worker => :foo_worker) will now ABORT the worker, it
2007 Dec 17
1
Some more updates, enhancements and fixes
Hi Folks, Well, Yesterday I pushed some more updates that I was cooking since last couple of days. Here is a brief list: 1. Results from worker stays even after a worker dies. 2. You can ask backgroundrb to store status objects in memcache cluster now. by default its stored in master process memory, but I have introduced an option to allow it to be stored in a memcache cluster:
2007 Dec 23
0
Updates and Fixes and more of awesome stuff
1. Whenever you ask BackgrounDRb to perform a particular task using: MiddleMan.ask_work(:worker => :rss_worker,:worker_method => :fetch_url, :data => "www.google.com") Your task would be performed then and there. But, if your worker is busy, task won''t be queued, except in socket buffer. And your request may get lost. This isn''t generally a problem
2008 May 05
2
Deploying to a staging server using Capistrano: how to start up BackgrounDRb?
Hi. I am using BackgrounDRb to process thumbnails and upload to S3 - things are hunky-dory in development (thumbs are generated, these are uploaded to S3, the metadata is saved to trhe DB, and I get a nice status page updated by periodic calls via ask_status), but when I tried to deploy to our staging server and stop/start BackgrounDRb via Capistrano, things blew up - well, not exactly,
2006 Oct 30
1
new BackgroundRB
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
2007 Dec 17
11
BackgrounDRb release 1.0 available now
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
2007 Jan 15
2
Backgroundrb keeps spawning processes
Hi! I''ve just a created a really simple rails scheduled worker for backgroundrb to start playing with : class SessionCleanerWorker < BackgrounDRb::Worker::RailsBase def do_work(args) logger.info "SessionCleaner> started" CGI::Session::ActiveRecordStore::Session.destroy_all( [''updated_at <?'', 120.minutes.ago] )
2008 Jan 10
8
Worker suicide
I have a worker which wants to delete itself after it finishes its work- how can it do that? Best Regards, Danny Burkes
2006 Oct 30
11
BackgrounDRb 0.2.0 Release! Complete rewrite.
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
2008 Mar 20
2
can''t call any methods on workers
Hi, I''m a long time backgroundrb user, still stuck using the very ancient original version from Ezra (not even Ezra''s 2.0 version, I''m using the one that didn''t really have a version number). The 2.0 version did very little but crash for me. Anyway I finally got some time set aside to try out this new version you all have been developing.
2008 Mar 27
0
lazy_load config bug
Hi there, This is in master_worker.rb at 266 - it looks to me that there is a bug in reading the lazy_loading property. The line below doesn''t work if lazy_load: true is specified in the yml. lazy_load = CONFIG_FILE[:backgroundrb][:lazy_load].nil? ? true : CONFIG_FILE[:backgroundrb][:lazy_load].nil? should say something like this: lazy_load = CONFIG_FILE[:backgroundrb][:lazy_load]
2007 Jun 04
2
backgroundrb scheduler
I''ve been having a terrible time with the backgroundrb scheduler. The issues I''m having is that the scheduled actions aren''t ran at all and if they do, the process stays around forever. I''m using the backgroundrb as a nightly cron to run some accounting operations. questions: 1. How can I have the process destroyed after the worker completes? 2. Any idea on
2006 May 25
1
New BackgrounDRb release
Friends- There is a new release of BackgrounDRb. This time it is a full fledged rails plugin with generators and rake tasks thanks to Saimon Moore. Thanks Saimon! You can read all about it here on my blog: http://brainspl.at/articles/2006/05/25/backgroundrb-new-release The newest feature besides the much cleaner way to install and control the drb server is caching. You can now use
2007 Jan 30
1
Backgroundrb weirdness with multiple mongrels
Hi list, I''m having some issues getting backgroundrb to play nice with more than one mongrel. When I run my app on a single mongrel instance it works fine. I have two different problems show up in my backgrounrb_server.log. The top of the backtrace is shown here: 20070130-12:03:03 (92473) failed to find slave socket - (RuntimeError) 20070130-12:03:03 (92473)
2008 Mar 11
1
Worker logging in test output.
Hi, I''m trying to silence the information that backgroundrb is putting in to my test runs. I''m seeing several hundred lines of this during the test runs (both unit and functional): {:type=>:all_worker_info} {:type=>:do_work, :worker=>:xmlrpc_xmpp_worker, :worker_method=>:register_user,
2007 Nov 30
1
backgroundrb not cleaning up tmp files?
I just had an interesting issue on a production system that has been running nicely for about a year. There were approximately 10,000 backgroundrb temp files in the /tmp directory. It looks like backgroundrb wasn''t cleaning them up. I noticed it with the following error: DRb::DRbConnError: drbunix:///tmp/backgroundrb.20015/ backgroundrb_logger_0_0.101544829808665 -
2007 Oct 25
3
Mocking Workers in Backgroundrb
Hi Has anyone mocked a call like the following for backgroundrb? MiddleMan.new_worker(:class => :admin_email_worker, :args => params [:email]) I cannot seem to find the correct manner to do it. Would have liked to be able to do MiddleMan.should_receive (:new_worker).with(:class => :admin_email_worker, :args => {"body" => "my message"}) Cheers Shane
2007 Apr 27
0
Backgroundrb running under cygwin - having issue with Railsbase workers
Hello all, We''re currently running version .1.x in our environment. We would like to move to .2.x to take advantage of some of the improvements made running in a multi-process environment. We deploy to a linux environment but develop locally in Windows. I''m aware that a number of people have reported the ability to run .2.x of backgroundrb inside cygwin, and for the most part,
2008 Jan 17
3
periodic scheduling
I''ve been using backgroundrb since back in March 2007 or so. It''s been working mostly OK for me, but since the old version doesn''t seem to work out of the box with rails 2.0 for me, I decided to test out the latest version. So, I''m looking at the scheduling, and trying to figure out the best option for what I want to do. What I have is a set of workers that
2006 Jul 24
0
Mongrel + BackgrounDRb + File Column = Upload Progress Bar?
Hi there, I''ve been digging around trying to find some information (mostly examples) on how one would handle a progress bar upload using BackgrounDRb and File Column. I did read http://backgroundrb.rubyforge.org/ and Ezra''s blog of course, but I still have a few questions. I made a simple upload form (as a test) that is submitted to the "upload_song" action. def