Jon: Can you reproduce this error on a fresh merb app? If you can't reproduce it on a fresh app then:
Is this the entire backtrace? I see this error sometimes when I have a syntax error in an action of my controller. Like if you typoed, hit save and such. What controller/action pair is this coming from? I'd start my search there. I know upgrading is always a pain. -ian On 14:48 Sat 06 Mar , Jon Hancock wrote: > I'm trying to use the published 1.1.0.pre gems. > After updating Gemfile, config.ru, etc by comparing to a newly merb- > gen'd app, I thought I had all the pieces in place (I was using > 1.1.0.pre from a git build as of December and all worked well). > > Now that I have merb up (using thin), the app mostly works, but now > I'm getting this hard to debug exception which "seems" to come from > haml. I tried downgrading haml to 2.2.16 to match what I was using > prior to the upgrade, but same error: > > merb : worker (port 4100) ~ wrong number of arguments (0 for 2) - > (ArgumentError) > /Users/jhancock/ruby-191-p243/lib/ruby/gems/1.9.1/gems/merb- > core-1.1.0.pre/lib/merb-core/controller/abstract_controller.rb:321:in > `_call_action' > /Users/jhancock/ruby-191-p243/lib/ruby/gems/1.9.1/gems/merb- > core-1.1.0.pre/lib/merb-core/controller/abstract_controller.rb:289:in > `block in _dispatch' > /Users/jhancock/ruby-191-p243/lib/ruby/gems/1.9.1/gems/merb- > core-1.1.0.pre/lib/merb-core/controller/abstract_controller.rb:284:in > `catch' > /Users/jhancock/ruby-191-p243/lib/ruby/gems/1.9.1/gems/merb- > core-1.1.0.pre/lib/merb-core/controller/abstract_controller.rb:284:in > `_dispatch' > /Users/jhancock/ruby-191-p243/lib/ruby/gems/1.9.1/gems/merb- > core-1.1.0.pre/lib/merb-core/controller/merb_controller.rb:285:in > `_dispatch' > /Users/jhancock/ruby-191-p243/lib/ruby/gems/1.9.1/gems/merb- > core-1.1.0.pre/lib/merb-core/controller/merb_controller.rb:262:in > `_call' > /Users/jhancock/ruby-191-p243/lib/ruby/gems/1.9.1/gems/merb- > core-1.1.0.pre/lib/merb-core/controller/merb_controller.rb:252:in > `call' > /Users/jhancock/ruby-191-p243/lib/ruby/gems/1.9.1/gems/merb- > core-1.1.0.pre/lib/merb-core/dispatch/dispatcher.rb:100:in > `dispatch_action' > /Users/jhancock/ruby-191-p243/lib/ruby/gems/1.9.1/gems/merb- > core-1.1.0.pre/lib/merb-core/dispatch/dispatcher.rb:76:in `handle' > /Users/jhancock/ruby-191-p243/lib/ruby/gems/1.9.1/gems/merb- > core-1.1.0.pre/lib/merb-core/dispatch/dispatcher.rb:36:in `handle' > /Users/jhancock/ruby-191-p243/lib/ruby/gems/1.9.1/gems/merb- > core-1.1.0.pre/lib/merb-core/rack/application.rb:17:in `call' > /Users/jhancock/ruby-191-p243/lib/ruby/gems/1.9.1/gems/haml-2.2.20/lib/ > sass/plugin/merb.rb:31:in `call_with_sass' > /Users/jhancock/ruby-191-p243/lib/ruby/gems/1.9.1/gems/thin-1.2.7/lib/ > thin/connection.rb:76:in `block in pre_process' > /Users/jhancock/ruby-191-p243/lib/ruby/gems/1.9.1/gems/thin-1.2.7/lib/ > thin/connection.rb:74:in `catch' > /Users/jhancock/ruby-191-p243/lib/ruby/gems/1.9.1/gems/thin-1.2.7/lib/ > thin/connection.rb:74:in `pre_process' > /Users/jhancock/ruby-191-p243/lib/ruby/gems/1.9.1/gems/thin-1.2.7/lib/ > thin/connection.rb:57:in `process' > /Users/jhancock/ruby-191-p243/lib/ruby/gems/1.9.1/gems/thin-1.2.7/lib/ > thin/connection.rb:42:in `receive_data' > /Users/jhancock/ruby-191-p243/lib/ruby/gems/1.9.1/gems/ > eventmachine-0.12.10/lib/eventmachine.rb:256:in `run_machine' > /Users/jhancock/ruby-191-p243/lib/ruby/gems/1.9.1/gems/ > eventmachine-0.12.10/lib/eventmachine.rb:256:in `run' > /Users/jhancock/ruby-191-p243/lib/ruby/gems/1.9.1/gems/thin-1.2.7/lib/ > thin/backends/base.rb:57:in `start' > /Users/jhancock/ruby-191-p243/lib/ruby/gems/1.9.1/gems/thin-1.2.7/lib/ > thin/server.rb:156:in `start' > /Users/jhancock/ruby-191-p243/lib/ruby/gems/1.9.1/gems/merb- > core-1.1.0.pre/lib/merb-core/rack/adapter/thin.rb:30:in `start_server' > /Users/jhancock/ruby-191-p243/lib/ruby/gems/1.9.1/gems/merb- > core-1.1.0.pre/lib/merb-core/rack/adapter/abstract.rb:298:in > `start_at_port' > /Users/jhancock/ruby-191-p243/lib/ruby/gems/1.9.1/gems/merb- > core-1.1.0.pre/lib/merb-core/rack/adapter/abstract.rb:131:in `start' > /Users/jhancock/ruby-191-p243/lib/ruby/gems/1.9.1/gems/merb- > core-1.1.0.pre/lib/merb-core/server.rb:174:in `bootup' > /Users/jhancock/ruby-191-p243/lib/ruby/gems/1.9.1/gems/merb- > core-1.1.0.pre/lib/merb-core/server.rb:42:in `start' > /Users/jhancock/ruby-191-p243/lib/ruby/gems/1.9.1/gems/merb- > core-1.1.0.pre/lib/merb-core.rb:165:in `start' > /Users/jhancock/ruby-191-p243/lib/ruby/gems/1.9.1/gems/merb- > core-1.1.0.pre/bin/merb:20:in `<top (required)>' > /Users/jhancock/ruby/bin/merb:19:in `load' > /Users/jhancock/ruby/bin/merb:19:in `<main>' > > Any ideas on how to debug this? I was looking forward to this upgrade > to fix run_later, which I desperately need. > > thanks, Jon > > -- > You received this message because you are subscribed to the Google Groups > "merb" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/merb?hl=en. > -- You received this message because you are subscribed to the Google Groups "merb" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/merb?hl=en.
