`heroku console' broken by the latest json dependency update (conflicts with cucumber) about legacy-cli HOT 4 CLOSED

heroku console is working for me. What error are you seeing?

from legacy-cli.

Here is what I get :

gemruby-1.9.2-p136 [/dev/_p/arrrrug(master) ]gem update heroku
/Users/aravet/.rvm/rubies/ruby-1.9.2-p136/bin/gem:4: warning: Insecure world writable dir /usr/local/bin in PATH, mode 040777
Updating installed gems
Updating heroku
Building native extensions. This could take a while...
Successfully installed json-1.5.1
Successfully installed heroku-1.18.0
Gems updated: json, heroku
Installing ri documentation for json-1.5.1...
Installing ri documentation for heroku-1.18.0...
Installing RDoc documentation for json-1.5.1...
Installing RDoc documentation for heroku-1.18.0...
ruby-1.9.2-p136 [/dev/_p/arrrrug(master) ]heroku console --app XXXXXXX
/Users/aravet/.rvm/gems/ruby-1.9.2-p136/gems/bundler-1.0.10/lib/bundler.rb:207: warning: Insecure world writable dir /usr/local/bin in PATH, mode 040777
/Users/aravet/.rvm/gems/ruby-1.9.2-p136/gems/bundler-1.0.10/lib/bundler/runtime.rb:31:in block in setup': You have already activated json 1.5.1, but your Gemfile requires json 1.4.6. Consider using bundle exec. (Gem::LoadError) from /Users/aravet/.rvm/gems/ruby-1.9.2-p136/gems/bundler-1.0.10/lib/bundler/spec_set.rb:12:inblock in each'
from /Users/aravet/.rvm/gems/ruby-1.9.2-p136/gems/bundler-1.0.10/lib/bundler/spec_set.rb:12:in each' from /Users/aravet/.rvm/gems/ruby-1.9.2-p136/gems/bundler-1.0.10/lib/bundler/spec_set.rb:12:ineach'
from /Users/aravet/.rvm/gems/ruby-1.9.2-p136/gems/bundler-1.0.10/lib/bundler/runtime.rb:17:in setup' from /Users/aravet/.rvm/gems/ruby-1.9.2-p136/gems/bundler-1.0.10/lib/bundler.rb:107:insetup'
from /users/aravet/dev/_p/arrrrug/config/boot.rb:8:in <top (required)>' from <internal:lib/rubygems/custom_require>:29:inrequire'
from internal:lib/rubygems/custom_require:29:in require' from /users/aravet/dev/_p/arrrrug/config/application.rb:1:in<top (required)>'
from internal:lib/rubygems/custom_require:29:in require' from <internal:lib/rubygems/custom_require>:29:inrequire'
from /users/aravet/dev/_p/arrrrug/config/environment.rb:2:in <top (required)>' from <internal:lib/rubygems/custom_require>:29:inrequire'
from internal:lib/rubygems/custom_require:29:in require' from /users/aravet/dev/_p/arrrrug/config.ru:3:in<top (required)>'
from /Users/aravet/.heroku/plugins/heroku_tab_complete_console/lib/console_environment.rb:25:in load' from /Users/aravet/.heroku/plugins/heroku_tab_complete_console/lib/console_environment.rb:25:increate_binding'
from /Users/aravet/.heroku/plugins/heroku_tab_complete_console/lib/heroku_tab_complete_console.rb:37:in setup_tab_complete' from /Users/aravet/.heroku/plugins/heroku_tab_complete_console/lib/heroku_tab_complete_console.rb:23:inconsole_session_with_tab_complete'
from /Users/aravet/.rvm/gems/ruby-1.9.2-p136/gems/heroku-1.18.0/lib/heroku/commands/app.rb:156:in console' from /Users/aravet/.heroku/plugins/heroku_colorize_console/lib/heroku_colorize_console.rb:37:inconsole_with_colorize'
from /Users/aravet/.rvm/gems/ruby-1.9.2-p136/gems/heroku-1.18.0/lib/heroku/command.rb:48:in run_internal' from /Users/aravet/.rvm/gems/ruby-1.9.2-p136/gems/heroku-1.18.0/lib/heroku/command.rb:20:inrun'
from /Users/aravet/.rvm/gems/ruby-1.9.2-p136/gems/heroku-1.18.0/bin/heroku:13:in <top (required)>' from /Users/aravet/.rvm/gems/ruby-1.9.2-p136/bin/heroku:19:inload'
from /Users/aravet/.rvm/gems/ruby-1.9.2-p136/bin/heroku:19:in `

from legacy-cli.

Looks like you have two plugins heroku_tab_complete_console and heroku_colorize_console that are causing this. Try removing those and see if you still get the error.

from legacy-cli.

Yes, you're right: uninstalling 'heroku_tab_complete_console' solved the problem.

from legacy-cli.