hi -

upgraded merb today and it now fails to boot. getting the following
problem...

/Library/Ruby/Gems/1.8/gems/merb-core-0.9.9/lib/merb-core/controller/
template.rb:127:in `compile_template': wrong number of arguments (3
for 4) (ArgumentError)


[EMAIL PROTECTED]:merbquest/trunk]$ merb

Loading init file from /Users/dc/svn/merbquest/trunk/config/init.rb
Loading /Users/dc/svn/merbquest/trunk/config/environments/
development.rb
 ~ Loaded DEVELOPMENT Environment...
 ~ loading gem 'merb-cache' ...
 ~ loading gem 'dm-ar-finders' ...
 ~ loading gem 'merb_paginate' ...
 ~ loading gem 'merb-assets' ...
 ~ loading gem 'dm-aggregates' ...
 ~ loading gem 'merb_helpers' ...
 ~ loading gem 'dm-validations' ...
 ~ loading gem 'dm-types' ...
 ~ loading gem 'dm-timestamps' ...
 ~ loading gem 'merb_param_protection' ...
 ~ loading gem 'actionmailer' ...
 ~ loading gem 'dm-tags' ...
 ~ loading gem 'merb_datamapper' ...
 ~ loading gem 'dm-core' ...
Logging to file at /Users/dc/svn/merbquest/trunk/log/development.log

/Library/Ruby/Gems/1.8/gems/merb-core-0.9.9/lib/merb-core/controller/
template.rb:127:in `compile_template': wrong number of arguments (3
for 4) (ArgumentError)
        from /Library/Ruby/Gems/1.8/gems/merb-core-0.9.9/lib/merb-core/
controller/template.rb:127:in `inline_template'
        from /Library/Ruby/Gems/1.8/gems/merb-core-0.9.9/lib/merb-core/
bootloader.rb:998:in `run'
        from /Library/Ruby/Gems/1.8/gems/merb-core-0.9.9/lib/merb-core/
bootloader.rb:997:in `each'
        from /Library/Ruby/Gems/1.8/gems/merb-core-0.9.9/lib/merb-core/
bootloader.rb:997:in `run'
        from /Library/Ruby/Gems/1.8/gems/merb-core-0.9.9/lib/merb-core/
bootloader.rb:96:in `run'
        from /Library/Ruby/Gems/1.8/gems/merb-core-0.9.9/lib/merb-core/
server.rb:170:in `bootup'
        from /Library/Ruby/Gems/1.8/gems/merb-core-0.9.9/lib/merb-core/
server.rb:42:in `start'
        from /Library/Ruby/Gems/1.8/gems/merb-core-0.9.9/lib/merb-core.rb:
123:in `start'
        from /Library/Ruby/Gems/1.8/gems/merb-core-0.9.9/bin/merb:11
        from /usr/bin/merb:27:in `load'
        from /usr/bin/merb:27


the error line in question is:
        engine_for(full_file_path).compile_template(io,
template_name(full_file_path), locals, mod)

in context is:


    # Takes a template at a particular path and inlines it into a
module and
    # adds it to the METHOD_LIST table to speed lookup later.
    #
    # ==== Parameters
    # io<#path>::
    #   An IO that responds to #path (File or VirtualFile)
    # locals<Array[Symbol]>::
    #   A list of local names that should be assigned in the template
method
    #   from the arguments hash. Defaults to [].
    # mod<Module>::
    #   The module to put the compiled method into. Defaults to
    #   Merb::InlineTemplates
    #
    # ==== Notes
    # Even though this method supports inlining into any module, the
method
    # must be available to instances of AbstractController that will
use it.
    #---
    # @public
    def inline_template(io, locals=[], mod = Merb::InlineTemplates)
      full_file_path = File.expand_path(io.path)
      engine_neutral_path = full_file_path.gsub(/\.[^\.]*$/, "")

      SUPPORTED_LOCALS_LIST[engine_neutral_path] |= locals unless
locals.empty?
      ret = METHOD_LIST[engine_neutral_path] =
        engine_for(full_file_path).compile_template(io,
template_name(full_file_path), locals, mod)

      io.close
      ret
    end


any thoughts on how to get this working? i tried edge and stable:
  sudo thor merb:stable

with the same results...

it seems odd that merb "stable" won't even boot,
but i cant think of anything in our environment that would be special
at the steps above...

ps this is on OS-X

/dc
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to