Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

This project is archived and is in readonly mode.

Possible edge rails bug

#6271

Steps to reproduce:

  1. rails new testapp -T -J --edge
  2. cd testapp
  3. edit Gemfile
source 'http://rubygems.org'

gem 'rails', :git => 'git://github.com/rails/rails.git'
gem 'arel', :git => 'git://github.com/rails/arel.git'
gem 'rack', :git => 'git://github.com/rack/rack.git'

gem 'sqlite3-ruby', :require => 'sqlite3'
  1. bundle install
  2. open something that should not be routable - http://localhost:3000/something

browser shows 500 error

log:

  /home/bug/.rvm/gems/ruby-1.9.2-p136/bundler/gems/rails-366e7854ac41/activesupport/lib/active_support/backtrace_cleaner.rb:72:in `block in filter'
  /home/bug/.rvm/gems/ruby-1.9.2-p136/bundler/gems/rails-366e7854ac41/activesupport/lib/active_support/backtrace_cleaner.rb:71:in `each'
  /home/bug/.rvm/gems/ruby-1.9.2-p136/bundler/gems/rails-366e7854ac41/activesupport/lib/active_support/backtrace_cleaner.rb:71:in `filter'
  /home/bug/.rvm/gems/ruby-1.9.2-p136/bundler/gems/rails-366e7854ac41/activesupport/lib/active_support/backtrace_cleaner.rb:26:in `clean'
  /home/bug/.rvm/gems/ruby-1.9.2-p136/bundler/gems/rails-366e7854ac41/actionpack/lib/action_dispatch/middleware/show_exceptions.rb:151:in `clean_backtrace'
  /home/bug/.rvm/gems/ruby-1.9.2-p136/bundler/gems/rails-366e7854ac41/actionpack/lib/action_dispatch/middleware/show_exceptions.rb:138:in `application_trace'
  /home/bug/.rvm/gems/ruby-1.9.2-p136/bundler/gems/rails-366e7854ac41/actionpack/lib/action_dispatch/middleware/show_exceptions.rb:132:in `block in log_error'
  /home/bug/.rvm/gems/ruby-1.9.2-p136/bundler/gems/rails-366e7854ac41/activesupport/lib/active_support/deprecation/reporting.rb:22:in `silence'
  /home/bug/.rvm/gems/ruby-1.9.2-p136/bundler/gems/rails-366e7854ac41/actionpack/lib/action_dispatch/middleware/show_exceptions.rb:129:in `log_error'
  /home/bug/.rvm/gems/ruby-1.9.2-p136/bundler/gems/rails-366e7854ac41/actionpack/lib/action_dispatch/middleware/show_exceptions.rb:64:in `render_exception'
  /home/bug/.rvm/gems/ruby-1.9.2-p136/bundler/gems/rails-366e7854ac41/actionpack/lib/action_dispatch/middleware/show_exceptions.rb:59:in `call'
  /home/bug/.rvm/gems/ruby-1.9.2-p136/bundler/gems/rails-366e7854ac41/railties/lib/rails/rack/logger.rb:13:in `call'
  /home/bug/.rvm/gems/ruby-1.9.2-p136/bundler/gems/rack-d7a3bb216845/lib/rack/runtime.rb:17:in `call'
  /home/bug/.rvm/gems/ruby-1.9.2-p136/bundler/gems/rails-366e7854ac41/activesupport/lib/active_support/cache/strategy/local_cache.rb:72:in `call'
  /home/bug/.rvm/gems/ruby-1.9.2-p136/bundler/gems/rack-d7a3bb216845/lib/rack/lock.rb:34:in `call'
  /home/bug/.rvm/gems/ruby-1.9.2-p136/bundler/gems/rails-366e7854ac41/actionpack/lib/action_dispatch/middleware/static.rb:60:in `call'
  /home/bug/.rvm/gems/ruby-1.9.2-p136/bundler/gems/rails-366e7854ac41/railties/lib/rails/engine.rb:414:in `call'
  /home/bug/.rvm/gems/ruby-1.9.2-p136/bundler/gems/rails-366e7854ac41/railties/lib/rails/railtie/configurable.rb:28:in `method_missing'
  /home/bug/.rvm/gems/ruby-1.9.2-p136/bundler/gems/rails-366e7854ac41/railties/lib/rails/rack/log_tailer.rb:14:in `call'
  /home/bug/.rvm/gems/ruby-1.9.2-p136/bundler/gems/rack-d7a3bb216845/lib/rack/handler/webrick.rb:52:in `service'
  /home/bug/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/webrick/httpserver.rb:111:in `service'
  /home/bug/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/webrick/httpserver.rb:70:in `run'
  /home/bug/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/webrick/server.rb:183:in `block in start_thread'

Reported by bug.odesk (at gmail) · January 10th, 2011 @ 07:58 AM

State: stale
Milestone: none
Assigned to: nobody
Importance: none

Activity

  1. dspencer
    dspencer

    +1, I was able to reproduce this. Before the stacktrace, though, I got these lines:

    Error during failsafe response: You have a nil object when you didn't expect it!
You might have expected an instance of Array.
The error occurred while evaluating nil.map

    January 10th, 2011 @ 08:25 PM

  2. rails
    rails
    • Tag changed from rails3.1 to rails31
    • State changed from new to open

    This issue has been automatically marked as stale because it has not been commented on for at least three months.

    The resources of the Rails core team are limited, and so we are asking for your help. If you can still reproduce this error on the 3-0-stable branch or on master, please reply with all of the information you have about it and add "[state:open]" to your comment. This will reopen the ticket for review. Likewise, if you feel that this is a very important feature for Rails to include, please reply with your explanation so we can consider it.

    Thank you for all your contributions, and we hope you will understand this step to focus our efforts where they are most helpful.

    April 11th, 2011 @ 01:00 AM

  3. rails
    rails
    • State changed from open to stale

    April 11th, 2011 @ 01:00 AM