uninitialized constant Slanger::VERSION (NameError) #93

Closed
benmcginnis opened this Issue Feb 14, 2013 · 3 comments

Comments

Projects
None yet
3 participants
@benmcginnis

If I try to startup slanger with the following command:
slanger -k [appkey] -s [appsecret] -w 0.0.0.0:8888 -a 0.0.0.0:22203 -v
, I get the following error:

~/.rvm/gems/ruby-1.9.3-p385/gems/slanger-0.3.6/bin/slanger:106:in `block in <top (required)>': uninitialized constant Slanger::VERSION (NameError)
    from ~/.rvm/gems/ruby-1.9.3-p385/gems/eventmachine-0.12.10/lib/eventmachine.rb:256:in `call'
    from ~/.rvm/gems/ruby-1.9.3-p385/gems/eventmachine-0.12.10/lib/eventmachine.rb:256:in `run_machine'
    from ~/.rvm/gems/ruby-1.9.3-p385/gems/eventmachine-0.12.10/lib/eventmachine.rb:256:in `run'
    from ~/.rvm/gems/ruby-1.9.3-p385/gems/slanger-0.3.6/bin/slanger:86:in `<top (required)>'
    from ~/.rvm/gems/ruby-1.9.3-p385/bin/slanger:19:in `load'
    from ~/.rvm/gems/ruby-1.9.3-p385/bin/slanger:19:in `<main>'
    from ~/.rvm/gems/ruby-1.9.3-p385/bin/ruby_noexec_wrapper:14:in `eval'
    from ~/.rvm/gems/ruby-1.9.3-p385/bin/ruby_noexec_wrapper:14:in `<main>'

And if I open up bin/slanger and comment out

puts "Running Slanger v.#{Slanger::VERSION}"

That solves the problem. Not sure why this is occurring for me.

@stevegraham

This comment has been minimized.

Show comment Hide comment
@stevegraham

stevegraham Feb 14, 2013

Owner

fixed!

Owner

stevegraham commented Feb 14, 2013

fixed!

@markburns

This comment has been minimized.

Show comment Hide comment
@markburns

markburns Apr 29, 2013

Collaborator

This is the commit that broke the build according to git bisect:

831fe68116d6fde72765f4d22fb8f99889bd8a5e is the first bad commit
commit 831fe68116d6fde72765f4d22fb8f99889bd8a5e
Author: Stevie Graham <sjtgraham@mac.com>
Date:   Thu Feb 14 01:28:17 2013 +0000

    move constant into slanger.rb. rev version, closes #93

:100644 100644 46dc85bdf06210dbeeede8e5e8280838b4d54923 9f137355c67cb2bb7372064a1849a55300326a71 M  Gemfile.lock
:100644 100644 d2ebe2fab5790a47dc0f43f2086416deb2e9b57d ee64fb5c69c145c0aedcd4c0ef8c8ed98cca1eca M  slanger.rb
Collaborator

markburns commented Apr 29, 2013

This is the commit that broke the build according to git bisect:

831fe68116d6fde72765f4d22fb8f99889bd8a5e is the first bad commit
commit 831fe68116d6fde72765f4d22fb8f99889bd8a5e
Author: Stevie Graham <sjtgraham@mac.com>
Date:   Thu Feb 14 01:28:17 2013 +0000

    move constant into slanger.rb. rev version, closes #93

:100644 100644 46dc85bdf06210dbeeede8e5e8280838b4d54923 9f137355c67cb2bb7372064a1849a55300326a71 M  Gemfile.lock
:100644 100644 d2ebe2fab5790a47dc0f43f2086416deb2e9b57d ee64fb5c69c145c0aedcd4c0ef8c8ed98cca1eca M  slanger.rb
@markburns

This comment has been minimized.

Show comment Hide comment
@markburns

markburns Apr 29, 2013

Collaborator

Actually wat? Just read the commit

Collaborator

markburns commented Apr 29, 2013

Actually wat? Just read the commit

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment