search for: gobigdave

Like most, I have a test and a production env. Both are CentOS 5, Ruby 1.8.6, Rails 2.0.2, MySQL 5, and Apache. Both were setup using the same procedure. Except for the hardware (test: Intel, prod: AMD) and memory (test: 512M, prod: 1G), both systems are essentially the same right down to the Rails env. Unfortunately, memory usage is very different for each. The test system has 2 mongrel

I have the following code: class User < ActiveRecord::Base has_many :requests do def find_active(options = {}) with_scope :find => { :conditions => ["requests.active = ?", true] } do find(:all, options) end end end end Executing user.requests.find_active results in the following SQL: SELECT * FROM requests WHERE (( requests.user_id = 10 ) AND (

I''m working on upgrading my app to the latest version of backgroundrb. Everything went find until I tried to execute my tasks. Here is my simple worker for testing: class MscWorker < BackgrounDRb::MetaWorker set_worker_name :msc_worker def create(args = nil) # this method is called, when worker is loaded for the first time end # Send a message to everyone def

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

Please tell me I''m just confused, but this is very strange. I have a migration like so: class AddLevelToRequest < ActiveRecord::Migration def self.up add_column :requests, :title_levels, :string end def self.down remove_column :requests, :title_levels end end Run the migration, and from the console do: >> r = Request.new => #<Request:0x31a243c

I recently switched over to v1.0, and things are rolling along pretty well. However, one thing that has always been a little confusing to me is knowing when to use thread_pool. Since most of my bgrb workers are called from my web app to process rather than being scheduled, I''m using the thread_pool for every call. Unfortunately, that means that I have to split up workers by how many

I have a previous question regarding long tasks and the thread_pool (sorry for the dup, I didn''t see the first go through). To try and track things down, I made a change based on a suggestion found in the archives. I moved my import contacts worker to its own file and set the pool_size to 1. class ImportContactsWorker < BackgrounDRb::MetaWorker set_worker_name

I''m having some trouble with using brb for polling for work. Basically, what I want to do is update the state of a record and have brb notice and start a process. I do not want to call ask_work for each process because there may be several places where the object''s state is changed, and I only want to process once. Plus, I can schedule things better this way. My first thought

I use backgroundrb for many long tasks in my system, but I''m having issues with one in particular. Two large tasks for me are importing people and updating companies. def import_contacts(args = nil) thread_pool.defer(args) do |job_id| begin job = ImportJob.find(job_id) job.process_job rescue => err logger.error "MscWorker#import_contacts

I use backgroundrb for many long tasks in my system, but I''m having issues with one in particular. Two large tasks for me are importing people and updating companies. def import_contacts(args = nil) thread_pool.defer(args) do |job_id| begin job = ImportJob.find(job_id) job.process_job rescue => err logger.error "MscWorker#import_contacts

I have the following in my environments.rb file: my_formats = { :msc => ''%d %b %Y %I:%M %p'', :msc_short => ''%d %b %Y'' } ActiveSupport::CoreExtensions::Time::Conversions::DATE_FORMATS.merge! (my_formats) ActiveSupport::CoreExtensions::Date::Conversions::DATE_FORMATS.merge! (my_formats) With this, things like

Now that Rails and many other gem/plugins have moved to github, there needs to be a better way to know where to get things from. The first thing I did was add github as a source (sudo gem sources -a http://gems.github.com/). How do I know where the gem came from once I install it? For example, Capistrano 2.4 seems to be in both places. Which one do I get when I install? If installed from