guard / guard-jasmine

The Swiss Army knife for automated Jasmine specs in your console.

Home Page:http://guard.github.io/guard-jasmine

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

"rake guard:jasmine" uninitialized constant Guard::Options

jnimety opened this issue · comments

after upgrading from guard 1.8.3 to 2.0.3

-    guard (1.8.3)
+    guard (2.0.3)
$ rake guard:jasmine
rake aborted!
uninitialized constant Guard::Options
/Users/jnimety/.rvm/gems/ruby-2.0.0-p247@control/gems/aws-s3-0.6.3/lib/aws/s3/extensions.rb:212:in `const_missing_from_s3_library'
/Users/jnimety/.rvm/gems/ruby-2.0.0-p247@control/gems/guard-2.0.3/lib/guard/ui.rb:33:in `options'
/Users/jnimety/.rvm/gems/ruby-2.0.0-p247@control/gems/guard-2.0.3/lib/guard/ui.rb:153:in `_filter'
/Users/jnimety/.rvm/gems/ruby-2.0.0-p247@control/gems/guard-2.0.3/lib/guard/ui.rb:172:in `_filtered_logger_message'
/Users/jnimety/.rvm/gems/ruby-2.0.0-p247@control/gems/guard-2.0.3/lib/guard/ui.rb:74:in `error'
/Users/jnimety/.rvm/gems/ruby-2.0.0-p247@control/gems/guard-jasmine-1.18.3/lib/guard/jasmine/cli.rb:222:in `rescue in spec'
/Users/jnimety/.rvm/gems/ruby-2.0.0-p247@control/gems/guard-jasmine-1.18.3/lib/guard/jasmine/cli.rb:166:in `spec'
/Users/jnimety/.rvm/gems/ruby-2.0.0-p247@control/gems/thor-0.18.1/lib/thor/command.rb:27:in `run'
/Users/jnimety/.rvm/gems/ruby-2.0.0-p247@control/gems/thor-0.18.1/lib/thor/invocation.rb:120:in `invoke_command'
/Users/jnimety/.rvm/gems/ruby-2.0.0-p247@control/gems/thor-0.18.1/lib/thor.rb:363:in `dispatch'
/Users/jnimety/.rvm/gems/ruby-2.0.0-p247@control/gems/thor-0.18.1/lib/thor/base.rb:439:in `start'
/Users/jnimety/.rvm/gems/ruby-2.0.0-p247@control/gems/guard-jasmine-1.18.3/lib/guard/jasmine/task.rb:37:in `block (2 levels) in initialize'
/Users/jnimety/.rvm/gems/ruby-2.0.0-p247@global/bin/ruby_noexec_wrapper:14:in `eval'
/Users/jnimety/.rvm/gems/ruby-2.0.0-p247@global/bin/ruby_noexec_wrapper:14:in `<main>'
Tasks: TOP => guard:jasmine
(See full trace by running task with --trace)

Hi, this is a Guard issue. I believe I fixed it in Guard master, can you confirm (put gem 'guard', github: 'guard' in your Gemfile)?

with gem 'guard', github: 'guard'

$ rake guard:jasmine                                                                                                                                                        <<<
15:59:41 - ERROR - undefined method `merge' for #<Guard::Options level=:info, template=":time - :severity - :message", time_format="%H:%M:%S">
rake aborted!
The spec couldn't be run: exit'
/Users/jnimety/.rvm/gems/ruby-2.0.0-p247@control/gems/guard-jasmine-1.18.3/lib/guard/jasmine/task.rb:44:in `rescue in block (2 levels) in initialize'
/Users/jnimety/.rvm/gems/ruby-2.0.0-p247@control/gems/guard-jasmine-1.18.3/lib/guard/jasmine/task.rb:36:in `block (2 levels) in initialize'
/Users/jnimety/.rvm/gems/ruby-2.0.0-p247@control/bin/ruby_noexec_wrapper:14:in `eval'
/Users/jnimety/.rvm/gems/ruby-2.0.0-p247@control/bin/ruby_noexec_wrapper:14:in `<main>'
Tasks: TOP => guard:jasmine
(See full trace by running task with --trace)

Hmmm I see what's the error... I'll see if that's possible to solve it in Guard... I'll be back!

Ok, I'm back with a fix pushed! Could you retry with Guard master and let me know how it goes? Thanks a lot!

fixed!

Awesome! 👍

I'm waiting for a confirmation for another (hopefully) fixed issue and I'll be able to release Guard 2.0.4 then!

Thanks!

Hmm I'm seeing a potential resurgence of this issue in version 2.0.0

/Users/piotr/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/guard-2.10.4/lib/guard/ui.rb:40:in `options': uninitialized constant Guard::Options (NameError)
    from /Users/piotr/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/guard-2.10.4/lib/guard/ui.rb:171:in `_filter'
    from /Users/piotr/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/guard-2.10.4/lib/guard/ui.rb:186:in `_filtered_logger_message'
    from /Users/piotr/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/guard-2.10.4/lib/guard/ui.rb:90:in `error'
    from /Users/piotr/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/guard-jasmine-2.0.0/lib/guard/jasmine/cli.rb:232:in `rescue in spec'
    from /Users/piotr/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/guard-jasmine-2.0.0/lib/guard/jasmine/cli.rb:236:in `spec'
    from /Users/piotr/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor/command.rb:27:in `run'
    from /Users/piotr/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor/invocation.rb:126:in `invoke_command'
    from /Users/piotr/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor.rb:359:in `dispatch'
    from /Users/piotr/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor/base.rb:440:in `start'
    from /Users/piotr/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/guard-jasmine-2.0.0/bin/guard-jasmine:3:in `<top (required)>'
    from /Users/piotr/.rbenv/versions/2.1.5/bin/guard-jasmine:23:in `load'
    from /Users/piotr/.rbenv/versions/2.1.5/bin/guard-jasmine:23:in `<main>'

I'll check it out...