Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

uninitialized constant Blazing::Hook::ERB #68

Closed
pabloalr opened this Issue · 13 comments

2 participants

@pabloalr

Just got this after running "blazing update" with gem at 0.2.11, and looks like my hooks are gone.

Had to downgrade to 0.2.10 to create the hooks again.

@effkay
Owner

can you post the full stack trace?

@pabloalr

Sure! Here it goes:

$ bundle exec blazing update staging
 ------> [blazing] INFO : Adding new remote staging pointing to mailee3@maileebeta.me:/home/mailee3/maileebeta.me
 ------> [blazing] INFO : Generating and uploading post-receive hook for staging
/Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/gems/blazing-0.2.11/lib/blazing/hook.rb:32:in `load_template': uninitialized constant Blazing::Hook::ERB (NameError)
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/gems/blazing-0.2.11/lib/blazing/hook.rb:52:in `generate_hook'
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/gems/blazing-0.2.11/lib/blazing/hook.rb:41:in `prepare_hook'
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/gems/blazing-0.2.11/lib/blazing/hook.rb:16:in `setup'
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/gems/blazing-0.2.11/lib/blazing/target.rb:30:in `update'
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/gems/blazing-0.2.11/lib/blazing/commands.rb:40:in `block in update'
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/gems/blazing-0.2.11/lib/blazing/commands.rb:40:in `each'
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/gems/blazing-0.2.11/lib/blazing/commands.rb:40:in `update'
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/gems/blazing-0.2.11/lib/blazing/commands.rb:8:in `run'
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/gems/blazing-0.2.11/lib/blazing/cli.rb:43:in `update'
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/gems/thor-0.14.6/lib/thor/task.rb:22:in `run'
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/gems/thor-0.14.6/lib/thor/invocation.rb:118:in `invoke_task'
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/gems/thor-0.14.6/lib/thor.rb:263:in `dispatch'
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/gems/thor-0.14.6/lib/thor/base.rb:389:in `start'
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/gems/blazing-0.2.11/bin/blazing:6:in `<top (required)>'
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/bin/blazing:23:in `load'
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/bin/blazing:23:in `<main>'
@effkay effkay closed this in 269ee17
@effkay effkay reopened this
@effkay
Owner

Can't reproduce this on my sandboxes, but I think I know where the problem is. Can you try running blazing update from blazing master? Just use 'blazing', :git => 'git://github.com/effkay/blazing.git' in your Gemfile.

@pabloalr
@pabloalr

Now I got

$ bundle exec blazing update staging
/Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/bundler/gems/blazing-269ee17d65d1/lib/blazing/recipe.rb:35:in `require': no such file to load -- blazing-269ee17d65d1 (LoadError)
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/bundler/gems/blazing-269ee17d65d1/lib/blazing/recipe.rb:35:in `block in load_recipes!'
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/bundler/gems/blazing-269ee17d65d1/lib/blazing/recipe.rb:35:in `each'
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/bundler/gems/blazing-269ee17d65d1/lib/blazing/recipe.rb:35:in `load_recipes!'
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/bundler/gems/blazing-269ee17d65d1/lib/blazing/config.rb:16:in `parse'
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/bundler/gems/blazing-269ee17d65d1/lib/blazing/commands.rb:18:in `initialize'
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/bundler/gems/blazing-269ee17d65d1/lib/blazing/commands.rb:8:in `new'
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/bundler/gems/blazing-269ee17d65d1/lib/blazing/commands.rb:8:in `run'
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/bundler/gems/blazing-269ee17d65d1/lib/blazing/cli.rb:43:in `update'
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/gems/thor-0.14.6/lib/thor/task.rb:22:in `run'
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/gems/thor-0.14.6/lib/thor/invocation.rb:118:in `invoke_task'
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/gems/thor-0.14.6/lib/thor.rb:263:in `dispatch'
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/gems/thor-0.14.6/lib/thor/base.rb:389:in `start'
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/bundler/gems/blazing-269ee17d65d1/bin/blazing:6:in `<top (required)>'
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/bin/blazing:23:in `load'
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/bin/blazing:23:in `<main>'
@effkay
Owner

Ok, just opened #69, as this is another issue you just uncovered. Thanks for the bug hunting ;-)

I just pushed a fix to master. Can you try again? (bundle update blazing before that of course)

@pabloalr

Hey, no problem! I'll fork and help you out.

Meanwhile, I just upgraded again and got:

$ bundle exec blazing update staging
 ------> [blazing] INFO : Adding new remote staging pointing to mailee3@maileebeta.me:/home/mailee3/maileebeta.me
 ------> [blazing] INFO : Generating and uploading post-receive hook for staging
/Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/bundler/gems/blazing-e6fdf46c128c/lib/blazing/hook.rb:32:in `load_template': uninitialized constant ERB (NameError)
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/bundler/gems/blazing-e6fdf46c128c/lib/blazing/hook.rb:52:in `generate_hook'
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/bundler/gems/blazing-e6fdf46c128c/lib/blazing/hook.rb:41:in `prepare_hook'
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/bundler/gems/blazing-e6fdf46c128c/lib/blazing/hook.rb:16:in `setup'
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/bundler/gems/blazing-e6fdf46c128c/lib/blazing/target.rb:30:in `update'
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/bundler/gems/blazing-e6fdf46c128c/lib/blazing/commands.rb:40:in `block in update'
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/bundler/gems/blazing-e6fdf46c128c/lib/blazing/commands.rb:40:in `each'
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/bundler/gems/blazing-e6fdf46c128c/lib/blazing/commands.rb:40:in `update'
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/bundler/gems/blazing-e6fdf46c128c/lib/blazing/commands.rb:8:in `run'
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/bundler/gems/blazing-e6fdf46c128c/lib/blazing/cli.rb:43:in `update'
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/gems/thor-0.14.6/lib/thor/task.rb:22:in `run'
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/gems/thor-0.14.6/lib/thor/invocation.rb:118:in `invoke_task'
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/gems/thor-0.14.6/lib/thor.rb:263:in `dispatch'
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/gems/thor-0.14.6/lib/thor/base.rb:389:in `start'
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/bundler/gems/blazing-e6fdf46c128c/bin/blazing:6:in `<top (required)>'
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/bin/blazing:23:in `load'
    from /Users/pablo/.rvm/gems/ruby-1.9.2-p320@mailee3/bin/blazing:23:in `<main>'
@effkay
Owner

Meh... that's the same error again. I thought this was the missing :: in front of ERB. Will need to have a closer look in a few minutes. And yes, of course, feel free to fork!

@effkay
Owner

Ok, was missing a require 'erb' apparently. Was able to reproduce your last error and fix it. Can you confirm?

@pabloalr
@pabloalr pabloalr closed this
@effkay
Owner

De nada :)

@effkay
Owner

Just released 0.2.12 with the fixes, hope you can deploy now :)

@pabloalr
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.