JSON error when trying db:pull (v1.17.5) about legacy-cli HOT 14 CLOSED

I was getting this too on any heroku command. Uninstalling and reinstalling this version fixed it too

from legacy-cli.

This should be fixed in 1.18.0, let me know if it works for you.

from legacy-cli.

hi all,
I've got this issue with Heroku 1.18.3. Looks like Fixnums can not be converted into json. Weirdly, it works well in local.
thanks.

Did

from legacy-cli.

Could you try this again and see if it's still failing for you?

from legacy-cli.

@ddollar. One more information. If I require 'json/pure' at the very top of the app launch (in the application.rb file before Bundler), the error is not there. I precise that I'm using heroku 1.18.3.

from legacy-cli.

no errors at all with heroku 1.18.2. Correction: it didn't work in local with the 1.18.3 version.
Hope it helps

from legacy-cli.

I recently updated the server side, could you try again with 1.18.3?

from legacy-cli.

still the same problem with 1.18.3 in both the local (normal since the gem didn't change) and heroku envs (btw I disabled require 'json/pure'). sorry :-(

from legacy-cli.

Try running the command with --debug appended and open a Heroku support ticket with the output. It will help as well if you grant us access to your database to try to reproduce.

Include the output of the following in the ticket:

gem list --local
gem env

from legacy-cli.

I'm having the same issue here and need to be able to move some data around from my stage to my production app. Has there been any progress? I tried adding

require "json/pure"

in my application.rb, but that didn't work. Neither did the solution here - http://blog.ethanvizitei.com/2010_11_01_archive.html, that is putting

class Fixnum
   def to_json(options = nil)
     to_s
   end
end

in an initializer, which seemed to work for him, but not for me.

from legacy-cli.

Could you try installing the latest heroku and taps gems with:

gem install heroku --pre
gem install taps --pre

And let me know if you still get this error?

from legacy-cli.

No - different error now, and not getting as far either. Breaks on "Receiving schema" with the following trace - http://pastie.org/1693805. Is there any chance I should be using a different version of json or something?

from legacy-cli.

I just pushed up 0.3.20.pre2 for taps, could you give that a shot?

from legacy-cli.

Golden! Working just fine now. Thanks!

from legacy-cli.