Many commands, e.g. ey init, ey help, are throwing a warning message on Ruby 2.2:
/Users/rad/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/engineyard-3.2.0/lib/engineyard/thor.rb:32: warning: circular argument reference - serverside_version
This was reported as a Ruby 2.2 bug: https://bugs.ruby-lang.org/issues/10314
However, Matz rejected the bug: https://bugs.ruby-lang.org/issues/10314#note-4. His recommendation is to change the code from foo = foo to foo = foo()
The bug was reopened as it broke Rails 3.2: https://bugs.ruby-lang.org/issues/10314#note-7. However the action taken there was to keep the Ruby 2.2 behavior and patch Rails 3.2 instead.
Based on the comments, the consensus seems to be on replacing the warning message with an error. If that is the case then a future version of Ruby will break the engineyard gem.
Many commands, e.g.
ey init,ey help, are throwing a warning message on Ruby 2.2:This was reported as a Ruby 2.2 bug: https://bugs.ruby-lang.org/issues/10314
However, Matz rejected the bug: https://bugs.ruby-lang.org/issues/10314#note-4. His recommendation is to change the code from
foo = footofoo = foo()The bug was reopened as it broke Rails 3.2: https://bugs.ruby-lang.org/issues/10314#note-7. However the action taken there was to keep the Ruby 2.2 behavior and patch Rails 3.2 instead.
Based on the comments, the consensus seems to be on replacing the warning message with an error. If that is the case then a future version of Ruby will break the engineyard gem.