search for: climes

Can anyone explain why BackgrounDRb is switching form DRb to SMTP protocol? That seems like a lot of overhead to add to the messaging back and forth? Orion

I''m getting the following error (when doing script/backgroundrb start) on my local machine, which is running os x 10.4.11. However, it works just fine on my linux server. RAILS_ROOT/vendor/plugins/backgroundrb/lib/../framework/nbio.rb:64:in `dump_object'': undefined method `write_nonblock'' for #<UNIXSocket: 0x135b5f4> (NoMethodError) I just grabbed the

Hi, just updated backgroundrb to release 1.0.1 and am getting this error when trying to start backgroundrb. vendor/plugins/backgroundrb/framework/core.rb:18: uninitialized constant Packet::ClassHelpers (NameError) Just updated from r298 where everything was working fine. If I comment out the offending line then backgroundrb starts but I can''t connect to it from my app. Anyone have any

is there an easy way to disable logging to backgroundrb_debug.log? Regards - reynard -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20080102/195dee18/attachment.html

...stuff. This is just a by product of using "packet" library. I know, thing is rough around the edge and needs more polish. But still, i hope it will be more stable than previous versions of backgroundrb. Please report all the bugs here. Thanks -- Let them talk of their oriental summer climes of everlasting conservatories; give me the privilege of making my own summer with my own coals. http://gnufied.org

Hey guys, I was playing with the cron trigger, and I noticed that wday is not honored. Looking at the code confirms this. Has anyone else seen this? Thanks Adam -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20071217/44d3a8a6/attachment.html

...t - Credits : ** Ezra Zygmuntowicz,skaar for taking BackgrounDRb so far. ** Kevin for helping out with OSX issues. ** Andy for patches and initial testing. ** Paul for patching up README. ** Other initial users. ** Matz, Francis for general inspiration. -- Let them talk of their oriental summer climes of everlasting conservatories; give me the privilege of making my own summer with my own coals. http://gnufied.org

I''m running the latest from svn (rev 285). I''ve been having a problem launching a process repeatedly. What happens is that I get a debug message "some read error" and then the worker refuses to run again. I''ve stripped my worker down to just doing a puts and it still happens. Like the other threads I want to launch my workers as needed, however I get the

Hello, Does reload_on_schedule force the worker to be reloaded even if it is already running? Or does it just load the worker if its not running when the schedule fires? I want to load the worker at the scheduled time if its not running, but I don''t want to reload the worker if its already running. Make sense? Thanks, Scott

...e user has been changed to BdrbConnError if rails is not able to connect to bdrb server. 3. loading mechanism has been changed, so remove backgroundrb script from your backgroundrb directory and do a rake backgroundrb:setup and you should be good to go. -- Let them talk of their oriental summer climes of everlasting conservatories; give me the privilege of making my own summer with my own coals. http://gnufied.org

...d thats how it runs timers and can trigger callbacks. So progress bar example, will have to reworked using callback mechanism, rather than threads. PS: trunk doesn''t yet reflect the changes i said. I will be checking in code soon. stay tuned. -- Let them talk of their oriental summer climes of everlasting conservatories; give me the privilege of making my own summer with my own coals. http://gnufied.org

Hi, I am trying to get the scheduling to work with my RoR application. How do I determine what version of backgroundrb I have configured? When I try to invoke??? rake backgroundrb:setup? , it fails. Thanks for the help. Linda

Hi All, When I add the line ''reload_on_schedule true'' to my worker, my tests will no longer run with the following exception: Starting ferret DRb server.../Users/revelation/projects/revelation-project/config/../lib/workers/alert_worker.rb:3: undefined method `reload_on_schedule'' for AlertWorker:Class (NoMethodError) class AlertWorker < BackgrounDRb::MetaWorker

Since moving to r296, I get warnings (" warning: already initialized constant...") for many of my class constants. This did not happen before, and I do not get the same warnings when loading my application normally. They are only warnings, so everything still runs, but I thought I would provide the FYI. -- Dave Dupre -------------- next part -------------- An HTML attachment was

Hi, I would like to use backgroundrb inside a story, been trying to set this up for a while, but I think the only solution is to use fixture files and unit testing. The problem is that every time I call a new worker, the test database gets wiped out, and only has available the records in fixture files. Instead, it would be great if the test database maintains its state throughout the

...lt the thread pool is of size 20. 5. Wrote examples on, how to use "connect" and "start_server" methods from backgroundrb workers. Again, consult documentation for it. Lets try/run it for a while and it will be released as 1.0 . -- Let them talk of their oriental summer climes of everlasting conservatories; give me the privilege of making my own summer with my own coals. http://gnufied.org

I''m working on an application that does extensive database searching. These searches can take a long time, so we have been working on moving the searches to a backgroundrb worker task so we can provide a sexy AJAX progress bar, and populate the search results as they are available. All of this seems to work fine until the size of the search results gets sufficiently large, when we start

...log: foreground :lazy_load: true :debug_log: false Those who have reported any bugs in past are requested to follow up and see if its fixed. I won''t suggest to run this in production straightaway, but do your testing first and then deploy. -- Let them talk of their oriental summer climes of everlasting conservatories; give me the privilege of making my own summer with my own coals. http://gnufied.org

Hi, I''m using backgroundrb 0.2.1 and having problem with worker processes staying around when the rails application does not explicitly delete them. Is there a way to automatically delete the worker processes when it has completed the job? Also does killing the process manually (using kill command) harm the backgroundrb server? I have some occasions where the backgroundrb server just

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