strange 'require' behavior in development environment

I have the exact same problem. And valentin's method of putting the require statement into the class definition actually helps. Seems very strange to me.

I can't reproduce the problem. Requiring outside the class works for me in both production and development.

ruby 1.8.7 (2010-01-10 patchlevel 249) [i686-linux]
Rails 3.0.0.beta3

Could not reproduce this error in Rails 2.3.5 (ruby 1.8.7 (2009-06-08 patchlevel 173) [universal-darwin10.0])

We used the following in our attempt to reproduce: (app/models/person.rb)

require 'open-uri'

class Person < ActiveRecord::Base
  def foo
    foo = open('http://google.com')
  end
end

I can confirm this is still happening here:

$ rails --version Rails 3.0.0.beta3
$ ruby --version ruby 1.9.2dev (2010-04-28 trunk 27525) [x86_64-darwin10.3.0]

My require statement is in a module defined in lib/foo.rb -- so it doesn't necessarily have to be in a controller or AR class.

However, the error is only generated when making a request to a controller that eventually hits the Module on the second attempt. The first attempt works fine, as do other routes that don't use the Module.

This issue occurs while running in development -- it does not occur while running in production

requiring open-uri at the top of environment.rb and removing it from all of my Modules 'fixes' this -- although it's definitely the wrong solution.

I am not able to recreate this problem with rails3 beta3. This is what I did.

rvm use ruby-1.8.7
rails g scaffold User name:string
rake db:migrate

# add following line at the top of app/models/user.rb
require 'open-uri'

rails s

I refreshed the page a number of times. All seems fine.

Some more info about my environment.

server booted with WEBrick

$ ruby -v
ruby 1.8.7 (2010-01-10 patchlevel 249) [i686-darwin10.3.0]

$ rails -v
Rails 3.0.0.beta3

Neeraj Singh, it is not the 'require' statement, that causes an error. Try to actually use open-uri in your code, like opening some URL in some of your model's methods, and that method should be called from the controller when you refresh the page.

About the second attempt - I was also getting this error on the second attempt.

I think, it is connected with class reloading in development mode. Everything is loaded as it has on the first attempt, but then, on the second attempt, when class is reloaded, something is not working correctly. It also explains why the error occurs in development mode only.

There are (AFAIK) two options to make this behave better:

• require open-uri in an initializer which will keep the remove_const bogeyman away

• use require_dependency instead of require, which will reload open-uri when the controller is reloaded

I can confirm this from the example app (rails 3.0.0.rc) in 1.9.2-rc2 and 1.8.7 ree.
All tests run fine, but development server breaks.