similar to: Migrations broken on trunk?

I really need some help here because I am at a loss. I have been using migrations just fine now for a while and I suddenly started getting a very bizarre error when migrations are run: undefined method `autoload_paths='' for Dependencies:Module I have tried rolling back my application code, and rolling back the rails edge revision I am running but neither seem to help. I have

Hi -- I''m upgrading an app from Rails 2.0.2 to 2.3.5 in development on a Mac OS/X Leopard. I unfroze the old Rails files, froze the 2.3.5 gem on the machine into the app, and some quick tests of the app showed no problems. However, after trying to run rake db:migrate, it fails silently. Run with trace I get the output below. I gather it might be related to plugin initialization or

I have setup passenger w/ apache, but my dashboard is not connecting properly. I am getting the following errors em::Specification#installation_path called from /etc/puppet/puppet-dashboard/vendor/rails/railties/lib/rails/vendor_gem_source_index.rb:93. NOTE: Gem::Specification#installation_path is deprecated, use base_dir. It will be removed on or after 2011-10-01.

I''m having some issues running rake commands for puppet dashboard. Here is one of the symptoms (see below). I''m a little new to setting up rails/rack applications, so I may be making a common mistake. It looks like gems are already packaged with dashboard, specifically rack-1.01. Should that gem just work out of the box? Command: rake RAILS_ENV=production reports:prune upto=1

I''m writing some code that accesses some lagacy database on PostgreSQL. Since the old database had some really ughly and weird naming conventions (like CamelCase). To work around this I created a second schema (named rails) in the same database and gave the tables and fields some rails-friendly names. The database user that Rails uses has its search_path set to the rails schema. That way

I''m getting the following error while connecting to mysql using activerecord-jdbcmysql-adapter (1.0.2). Rails 3.0.1. ActiveRecord::JDBCError: Generated keys not requested. You need to specify Statement.RETURN_GENERATED_KEYS to Statement.executeUpdate() or Connection.prepareStatement().: SET SQL_AUTO_IS_NULL=0 This occurs not matter what application I run it in to e.g. rake, rails

mini@mini:~/Sites/music_library$ rake db:migrate rake aborted! couldn''t parse YAML at line 28 column 6 /home/mini/my_gems/gems/railties-3.2.9/lib/rails/application/configuration.rb:115:in `database_configuration'' /home/mini/my_gems/gems/activerecord-3.2.9/lib/active_record/railtie.rb:78:in `block (2 levels) in <class:Railtie>''

Hi, I''m starting to use Test::Unit to create unit tests for my Rails Applications/Plugins. I don''t have much experience in Ruby Unit Testing. The problem is that the output report is very simple and it is very difficult to discover where is the error. Test::Unit does not show the line number of the error and the Stack Trace printed using the --trace option does not help either.

I have yet to find a solution for this issue I have tried multiple things that I have found on google, but yet have i found a solution. If someone could help me and point me in the right direction I would be much appreciated. Thanks. rake aborted! uninitialized constant Mysql::Error ** Invoke db:create (first_time) ** Invoke db:load_config (first_time) ** Invoke rails_env (first_time) **

HI All, I have installed the Active Admin successfully, but facing the following error while restarting the server after generating an resource. *rails generate active_admin:resource item* /home/logs/Desktop/training/RAILS/courier/app/admin/items.rb:1:in `<top (required)>'': uninitialized constant Item (NameError) from

Hello folks, I´m here trying to find the way to solve my problem. When i try to run rake db:create or rake db:create:all the process stops and the databases are not created. I change the directives, putting --trace before the rake db:create and the steps are C:\appws\cookbook>rake db:create --trace (in C:/appws/cookbook) ** Invoke db:create (first_time) ** Invoke db:load_config (first_time)

I''ve been working on an app, and had a friend check it out to his machine. I''ve got rails and all my plugins set up with svn:externals, so when he svn ups it he gets all the latest stuff. I''ve just svn up''d both machines so we''re running the same versions of everything. We''re also running the same version of ruby (1.8.4). As far as I can

Hello, I''ve been playing with this for hours, and got through a couple glitches (e.g. updating to Ruby 1.8.4) but this one is well beyond my N00b skills. When trying to run script/server I get: ./script/../config/../vendor/rails/activesupport/lib/active_support/dependencies.rb:87:in `as_load_path'': stack level too deep (SystemStackError) from

Hi! First of all, this is my first application on Rails, and i''m stuck at a migration. i created a demo app (the demo_app from michael hartl''s tutorial) as usual: rails new demo_app, rails generate scaffold User name:string email:string, and when i do rake db:migrate, this stack appears: rake db:migrate --trace ** Invoke db:migrate (first_time) ** Invoke environment

Hey guys! I am using rspec trunk, and I am having a little problem with the latest version. (I am quite sure this worked with an older version about a week ago) heres the spec: it "should render the new user form without layout for a xhr request" do @controller.should_receive(:render).with(:layout=>false) xhr :get,:new end and the controller: def new render

I have restful_authentication in use on an app and it has been working fine, but I recently was changing the account creation flow and needed to enable the UserObserver. I did so by including it in the environment.rb (config.active_record.observers = :user_observer) and Rails wouldn''t start. I got the following error; source/communitysites/vendor/rails/activerecord/lib/active_record/

Hi i try to run this rake db:migrate How i fix this i get this [root@localhost catarse]# rake db:migrate /usr/local/rvm/gems/ruby-1.9.3-p484/gems/activesupport-4.0.2/lib/active_support/dependencies.rb:229:in `block in require': iconv will be deprecated in the future, use String#encode instead. You no longer need to have jasmine.rake in your project, as it is now automatically

Because we''re now using views, I had to upgrade to mysql 5 on a project using Rails 1.0. Updated my mysql gem accordingly (which required upgrading xcode). Ruby 1.8.2, MacOS X (10.4.6) Worked fine several times (even before updating the mysql gem, then suddenly it just balked and stopped working, giving the spew below. Have also dropped (and recreated) both the test and

Running rails 1.1 and MySQL 5 on Kubuntu. I moved the same rails project from one machine to another. To set up the database I try to run `rake migrate` but I am greeted with the error/stack trace below. Any idea why this could be? It doesn''t seem to be a permissions problem--I can login to the database as my application just fine. I tried downgrading MySQL to v4.1 because that is

Hi, I am trying the tutorial in: http://guides.rubyonrails.org/getting_started.html when I try to navigate to http://localhost:3000 after the 4.3 change I get the error : ActiveRecord::ConnectionNotEstablished and I don''t know how to solve it the database.yml file is: adapter => mysql host => 127.0.0.1 database => blog username => root password => ***** my