similar to: ActiveRecord::Observers?

Hi there I''ve been running BackgroundRb in production for a few months now. Recently we added encryption onto some of our ActiveRecord fields by hooking in the before_save and after_save callbacks, like: class MyCallback def initialize(attr_names) @attr_names = attr_names end def before_save(model) @attr_names.each do |attr_name| next if

I have a pretty strange problem. Here is basically what I have to demonstrate my problem: class Event < ActiveRecord::Base def after_create AnotherClass.find_event(id) end end class AnotherClass < ActiveRecord::Base def self.find_event(event_id) e = Event.find event_id end end Here is the catch 22 and it''s quite annoying. Basically ActiveRecord puts to whole save

Hello all, I am interested in using BackgrounDRb to clear out ActiveRecord based sessions. I have this working, just with a small hitch, here is the code: class ClearSessionsWorker < BackgrounDRb::Rails repeat_every 7.minutes first_run Time.now def do_work(args) Session.destroy_all(["updated_at < ?", 20.minute.ago ]) end end It''s not very complicated and

Hi List, first of thank you Ezra for BackgroundRB. Very cool plugin indeed! This is a public service FYI. In case you are running postgres as your database backend and you are seeing the following errors in your backgroundrb.log: ActiveRecord::StatementInvalid: NoMethodError: undefined method `async_query'' for #<PGconn:0x22ed648>: You are using the postgres-pr adapter

I''m attempting to assign ActiveRecord Observers to some of my models, specified in config/environment.rb like so, config.active_record.observers = :presentation_observer, :asset_observer, :tag_observer My models use plugins which extend ActiveRecord::Base, including Sebastian Kanthak''s file_column Attempting to boot mongrel yields:

Hello I''m using the ''act_as_authenticated'' plugin to implement a small and simple authentication system in my app. Everything is working just fine and the world is a better place to live in. The plugin creates a ActiveRecord observer in order to send the newly registered user a confirmation e-mail. Per the API docs [1], one should declare the observer in the

Hey guys, Firstly, I''m new to the list and great work with backgroundrb, it''s sweet!!! I''ve just started noticing an issue and i''m wondering if there is a standard fix. The situation is as follows: 1. In my model''s after_save I call my worker asynchronously with the active record object''s id as a parameter (the record that has just

Greetings, I am seeing the following in my log quite a bit 20 + times per day. The stack-trace seems tin indicate an internal issue - is concurrency related? == 0.2.1 (Released November 28, 2006 - r162) My workers continue to function; on the next iteration I believe. Any thoughts are appreciated. cheers, Jodi allow_concurrency=true Scheduler.run failure: undefined method

Hi all, I just started using prototype 1.3.1. I''ve successfully used Form.Element.EventObserver on a select list and recently tried to add it to radio options. However, I think there is a flaw in how it works with radio options. Radio options are a little unusual in that there are multiple distinct elements, tied together by a common name, where changing one element causes a

Hi friends, I''ve a strange problem with ActiveRecord#find in a worker, this sometimes work fine and somethimes return Nil but the SQL query is fine, I don''t know what happen, I was worked a complete day on debugging this, here is my code: http://pastie.caboo.se/201986 Very thanks for your help. Regards. -- Rub?n D?vila Santos. http://rubenonrails.com -------------- next part

Hi! As you might remember I''m having a problem of backgroundrb stopping calling my workers after some period of time. I tried adding logging to backgroundrb source code but it didn''t help. So, after digging through internet I''ve found several gdb tools and here''s what I''ve discovered: After attaching to a backgroundrb ruby process it turns out that it

I have BackgrounDRb configured to handle two cases of long-running tasks: (1) on-demand user triggered requests for some action, and (2) scheduled background running of tasks on a predetermined schedule. In my particular case, we have a publication task that can take several minutes to perform. Users can setup a regular publication schedule, or can hit a ''publish now'' button to

(Sorry my last email had the wrong subject) Hi, I''ve just installed background rb 0.2.1. When I try start a worker in my application controller I receive the following error: wrong number of arguments (2 for 1) - (ArgumentError) /home/chris/projects/call_manager/trunk/call_manager_app/vendor/plugins/backgroundrb/server/lib/backgroundrb/middleman.rb:211:in `initialize''

I''ve been trying unsuccessfully for the better part of today to write a worker that can use by ActiveRecord model classes. The bizarre thing is that worker just stops at the point accessing the database connection. An exception isn''t raising, it just dies. My worker class is below, I''ve interspersed log messages throughout to try to determine where it is dying. =====

for some strange reason this error occours when i create one worker from another BUT only when i derive worker class from Worker::Base instead or Worker::RailsBase - when change it back it works fine, child worker can have empty do_work, but this error still ocours Bad file descriptor (Errno::EBADF) /var/lib/gems/1.8/gems/slave-1.2.0/lib/slave.rb:214:in `for_fd''

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,

Hello everyone, I''m stuck with this very obscure error whenever I try to create a new worker. My worker is a subclass of BackgrounDRb::Worker::RailsBase, and if you follow the stack trace below, you can tell that the error occurs while trying to load Rails. There is no problem starting up the server, by the way. Does anyone have any idea what might be causing this? I didn''t have

Hey, I have scheduled script that is not working very well. It will only run once or twice before I have to restart the server to get it running again. If I try to the worker manually after it has stopped exceuting the schedule I get this in the server log: 20070522-07:33:36 (5030) Connection reset by peer - (DRb::DRbConnError) 20070522-07:33:36 (5030) /usr/local/lib/ruby/1.8/drb/drb.rb:566:in

Hello - Can anyone explain why I get the stack trace in background_server.log when I try to start my first worker? I don''t get this on subsequent workers, only the first one. I should note, the method I am using to start backgroundrb is documented in the archives, and is likely the root of this problem. Suggestions about how to "fix" or avoid this issue are appreciated.

Hi, I have an application that receives XML files, and then hands each one off to a backgroundrb worker to parse and store the info. Everything was working, until I needed to support a larger character set. So I added the following to the top of my XML files: <?xml version="1.0" encoding="ISO-8859-1"?> Adding this worked fine when I tested it without using