Can not run `t authorize`, undefined method error from oauth.

Open
#326 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
ruby
Domain
cli

Research direction

Reproduce t authorize with Ruby 2.3.0 and RubyGems 2.5.1, then inspect the require path beginning at bin/t:7 and the reported oauth gem error. Compare the behavior with Ruby 2.2.2; done means authorization starts without the undefined this method error.

Written by the indexing model from the issue text.

Description

bug

I've just run a fresh install of t on Lubuntu.

On my first try of the t executable, to run authorize, I get this error, apparently coming from a gem spec.

$ t authorize
/home/ajfaraday/.rvm/rubies/ruby-2.3.0/lib/ruby/2.3.0/rubygems/specification.rb:2158:in `method_missing': undefined method `this' for #<Gem::Specification:0x61ca88 oauth-0.4.7> (NoMethodError)
        from /home/ajfaraday/.rvm/rubies/ruby-2.3.0/lib/ruby/2.3.0/rubygems/specification.rb:1057:in `find_active_stub_by_path'
        from /home/ajfaraday/.rvm/rubies/ruby-2.3.0/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:64:in `require'
        from /home/ajfaraday/.rvm/gems/ruby-2.3.0/gems/t-2.10.0/bin/t:7:in `<top (required)>'
        from /home/ajfaraday/.rvm/gems/ruby-2.3.0/bin/t:23:in `load'
        from /home/ajfaraday/.rvm/gems/ruby-2.3.0/bin/t:23:in `<main>'
        from /home/ajfaraday/.rvm/gems/ruby-2.3.0/bin/ruby_executable_hooks:15:in `eval'
        from /home/ajfaraday/.rvm/gems/ruby-2.3.0/bin/ruby_executable_hooks:15:in `<main>'

This same error is thrown in all ruby executables.

I'm using ruby 2.3.0 via rvm...

$ ruby -v
ruby 2.3.0p0 (2015-12-25 revision 53290) [x86_64-linux]
$ gem -v
2.5.1

Note: Changing back to ruby 2.2.2 fixed this issue.

Dominant language
Ruby
Stars
5.6k
Forks
402
Avg merge
13h 50m
Merged PRs (30d)
5

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sferik/x-cli

All issues in sferik/x-cli

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.