search

effkay / blazing

painless git push deployments for everyone
MIT License
80 stars 12 forks source link

uninitialized constant Blazing::Hook::ERB #68

Closed pabloalr closed 12 years ago

pabloalr commented 12 years ago

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 commented 12 years ago

can you post the full stack trace?

pabloalr commented 12 years ago

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 commented 12 years ago

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 commented 12 years ago

Sure, just a minute.

On Wed, Jul 11, 2012 at 6:18 PM, Felipe Kaufmann < reply@reply.github.com

wrote:

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.

Reply to this email directly or view it on GitHub: https://github.com/effkay/blazing/issues/68#issuecomment-6920088

pabloalr commented 12 years ago

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 commented 12 years ago

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 commented 12 years ago

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 commented 12 years ago

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 commented 12 years ago

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

pabloalr commented 12 years ago

Fix confirmed!

Thank you very much!

On Wed, Jul 11, 2012 at 6:47 PM, Felipe Kaufmann < reply@reply.github.com

wrote:

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

Reply to this email directly or view it on GitHub: https://github.com/effkay/blazing/issues/68#issuecomment-6920830

effkay commented 12 years ago

De nada :)

effkay commented 12 years ago

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

pabloalr commented 12 years ago

Yep! Like a charm :)

On Wed, Jul 11, 2012 at 7:00 PM, Felipe Kaufmann < reply@reply.github.com

wrote:

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

Reply to this email directly or view it on GitHub: https://github.com/effkay/blazing/issues/68#issuecomment-6921162