Could you try updating to the latest heroku (1.18.0) and taps (0.3.17) and see if you still have the issue?

from legacy-cli.

Works nicely now. Thanks.

from legacy-cli.

I'm having the same issue with latest heroku (heroku-gem/2.17.0) and taps (taps-0.3.23).

from legacy-cli.

I am also having this issue with the lastest heroku 2.17.0 and taps 0.3.23

from legacy-cli.

As Am I. Also using heroku 2.17.0 and taps 0.3.23

from legacy-cli.

Seeing the same issue using heroku 2.17.0 and taps 0.3.23

from legacy-cli.

Ditto.. Can someone reopen this please ?

from legacy-cli.

Also having the same issue with heroku 2.17.0 and taps 0.3.23

from legacy-cli.

BUMP! Still having issues with heroku 2.18.1 and taps 0.3.23.

from legacy-cli.

Those that are having issues:

• How did you install the CLI? Toolbelt or gem?
• What OS/version are you on?

And please paste the output of these commands:

which heroku
which ruby

from legacy-cli.

@ddollar: here you go
(venv)Ryans-MacBook-Pro:project rdpfeffer$ which heroku
/usr/bin/heroku

(venv)Ryans-MacBook-Pro:project rdpfeffer$ which ruby
/usr/bin/ruby

I followed the commands in the heroku docs to install both of these, running Mac OS X10.7

the commands that I am running:
heroku db:push postgres://mydbUser:mydbpass@localhost/mydb -f 'areacode' --remote staging1

from legacy-cli.

I had problems when I installed the Toolbelt for OSX 10.7

I fixed the problems by manually removing the heroku binary and then running:

$ sudo gem install --version '2.16.0' heroku

My stuff is located here:

$ which heroku
/usr/bin/heroku
$ which ruby
/usr/bin/ruby

from legacy-cli.

@rdpfeffer can you run the following in irb and then paste the output:

require "taps"
puts $:

And then run this from the command line and paste the output

gem env

from legacy-cli.

I installed the CLI via the gem

brent:~$ which heroku
/Users/brent/.rbenv/shims/heroku
brent:~$ which ruby
/Users/brent/.rbenv/shims/ruby

from legacy-cli.

Ryans-MacBook-Pro:project rdpfeffer$ irb

require "taps"
LoadError: no such file to load -- taps
from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:36:in gem_original_require' from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:36:inrequire'
from (irb):1
require taps
NameError: undefined local variable or method taps' for main:Object from (irb):2 put $: NoMethodError: undefined methodput' for main:Object
from (irb):3

Ryans-MacBook-Pro:project rdpfeffer$ gem env
RubyGems Environment:

• RUBYGEMS VERSION: 1.8.15
• RUBY VERSION: 1.8.7 (2010-01-10 patchlevel 249) [universal-darwin11.0]
• INSTALLATION DIRECTORY: /Library/Ruby/Gems/1.8
• RUBY EXECUTABLE: /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby
• EXECUTABLE DIRECTORY: /usr/bin
• RUBYGEMS PLATFORMS:
  • ruby
  • universal-darwin-11
• GEM PATHS:
  • /Library/Ruby/Gems/1.8
  • /Users/rdpfeffer/.gem/ruby/1.8
  • /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8
• GEM CONFIGURATION:
  • :update_sources => true
  • :verbose => true
  • :benchmark => false
  • :backtrace => false
  • :bulk_threshold => 1000
• REMOTE SOURCES:
  • http://rubygems.org/

from legacy-cli.

@ddollar I should also note that we are running python/django so we are not doing anything with ruby other than what the tools require

from legacy-cli.

irb(main):002:0> require 'taps'
LoadError: no such file to load -- taps
    from /Users/brent/.rbenv/versions/1.9.2-p290/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
    from /Users/brent/.rbenv/versions/1.9.2-p290/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
    from (irb):2
    from /Users/brent/.rbenv/versions/1.9.2-p290/bin/irb:12:in `<main>'
irb(main):003:0> puts $:
/Users/brent/.rbenv/versions/1.9.2-p290/lib/ruby/site_ruby/1.9.1
/Users/brent/.rbenv/versions/1.9.2-p290/lib/ruby/site_ruby/1.9.1/x86_64-darwin11.2.0
/Users/brent/.rbenv/versions/1.9.2-p290/lib/ruby/site_ruby
/Users/brent/.rbenv/versions/1.9.2-p290/lib/ruby/vendor_ruby/1.9.1
/Users/brent/.rbenv/versions/1.9.2-p290/lib/ruby/vendor_ruby/1.9.1/x86_64-darwin11.2.0
/Users/brent/.rbenv/versions/1.9.2-p290/lib/ruby/vendor_ruby
/Users/brent/.rbenv/versions/1.9.2-p290/lib/ruby/1.9.1
/Users/brent/.rbenv/versions/1.9.2-p290/lib/ruby/1.9.1/x86_64-darwin11.2.0
=> nil

RubyGems Environment:

• RUBYGEMS VERSION: 1.8.10
• RUBY VERSION: 1.9.2 (2011-07-09 patchlevel 290) [x86_64-darwin11.2.0]
• INSTALLATION DIRECTORY: /Users/brent/.rbenv/versions/1.9.2-p290/lib/ruby/gems/1.9.1
• RUBY EXECUTABLE: /Users/brent/.rbenv/versions/1.9.2-p290/bin/ruby
• EXECUTABLE DIRECTORY: /Users/brent/.rbenv/versions/1.9.2-p290/bin
• RUBYGEMS PLATFORMS:
  • ruby
  • x86_64-darwin-11
• GEM PATHS:
  • /Users/brent/.rbenv/versions/1.9.2-p290/lib/ruby/gems/1.9.1
  • /Users/brent/.gem/ruby/1.9.1
• GEM CONFIGURATION:
  • :update_sources => true
  • :verbose => true
  • :benchmark => false
  • :backtrace => false
  • :bulk_threshold => 1000
• REMOTE SOURCES:
  • http://rubygems.org/

from legacy-cli.

Here the output on my machine:

jknotzke@shampoo:$ which heroku
/usr/bin/heroku
jknotzke@shampoo:$ which ruby
/usr/bin/ruby
jknotzke@shampoo:~$ irb

require "taps"
LoadError: no such file to load -- taps
from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in gem_original_require' from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygems/custom_require.rb:31:inrequire'
from (irb):1
puts $:
/Library/Ruby/Site/1.8
/Library/Ruby/Site/1.8/powerpc-darwin11.0
/Library/Ruby/Site/1.8/universal-darwin11.0
/Library/Ruby/Site
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/vendor_ruby/1.8
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/vendor_ruby/1.8/universal-darwin11.0
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/vendor_ruby
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/powerpc-darwin11.0
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/universal-darwin11.0
.
=> nil
quit
jknotzke@shampoo:~$ gem env
RubyGems Environment:

• RUBYGEMS VERSION: 1.3.6
• RUBY VERSION: 1.8.7 (2010-01-10 patchlevel 249) [universal-darwin11.0]
• INSTALLATION DIRECTORY: /Library/Ruby/Gems/1.8
• RUBY EXECUTABLE: /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby
• EXECUTABLE DIRECTORY: /usr/bin
• RUBYGEMS PLATFORMS:
  • ruby
  • universal-darwin-11
• GEM PATHS:
  • /Library/Ruby/Gems/1.8
  • /Users/jknotzke/.gem/ruby/1.8
  • /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8
• GEM CONFIGURATION:
  • :update_sources => true
  • :verbose => true
  • :benchmark => false
  • :backtrace => false
  • :bulk_threshold => 1000
• REMOTE SOURCES:
  • http://rubygems.org/

from legacy-cli.

@ddollar @mliu7 FYI, switching back to heroku 2.16.0 worked for me too. Thanks for the tip. looking forward to getting the latest toolbelt fixed.

from legacy-cli.

Same issue, but even rolled back to 2.16.0 :(.

[jedwards@jayme-ubuntu:~/kinlighten] $ gem env
RubyGems Environment:

• RUBYGEMS VERSION: 1.8.6
• RUBY VERSION: 1.9.2 (2011-07-09 patchlevel 290) [i686-linux]
• INSTALLATION DIRECTORY: /home/jedwards/.rvm/gems/ruby-1.9.2-p290
• RUBY EXECUTABLE: /home/jedwards/.rvm/rubies/ruby-1.9.2-p290/bin/ruby
• EXECUTABLE DIRECTORY: /home/jedwards/.rvm/gems/ruby-1.9.2-p290/bin
• RUBYGEMS PLATFORMS:
  • ruby
  • x86-linux
• GEM PATHS:
  • /home/jedwards/.rvm/gems/ruby-1.9.2-p290
  • /home/jedwards/.rvm/gems/ruby-1.9.2-p290@global
• GEM CONFIGURATION:
  • :update_sources => true
  • :verbose => true
  • :benchmark => false
  • :backtrace => false
  • :bulk_threshold => 1000
• REMOTE SOURCES:
  • http://rubygems.org/

from legacy-cli.

Moving to 2.16.0 worked for me.

from legacy-cli.

P.S. This is with taps 0.3.23 and heroku 2.16.0 (the only versions installed).

from legacy-cli.

I'm seeing this as well; heroku 2.19.2, taps 0.3.23.

from legacy-cli.

Same error for me:
/usr/bin/heroku
heroku-gem/2.20.1

~/.rvm/rubies/ruby-1.9.3-p0/bin/ruby
[myapp]/vendor/bundle/ruby/1.9.1/gems/taps-0.3.23

Installed Heroku from the toolbelt.

It seems the last comment from Heroku was a month ago. Any progress on this? Perhaps a workaround?

from legacy-cli.

I'm digging around on this today. Sorry for the delay in response, but I've yet to have much luck reproducing this locally, which always makes things harder to track down.

from legacy-cli.

Is there perhaps a workaround?

Sent from my iPad, please excuse typos.

On 28 Feb 2012, at 21:54, Wesley [email protected] wrote:

I'm digging around on this today. Sorry for the delay in response, but I've yet to have much luck reproducing this locally, which always makes things harder to track down.

---

Reply to this email directly or view it on GitHub:
#69 (comment)

from legacy-cli.

@kakubei I can guess at one, but since I'm not having luck locally it is difficult to know for sure. Could you try: ruby -r rubygems /usr/bin/heroku db:push ...? I'm not sure it will help, but it shouldn't hurt.

from legacy-cli.

For those of you still having issues you might also consider using the pg backups addon to manage this sort of thing (and basic support is free). You can find info here: http://devcenter.heroku.com/articles/pgbackups

from legacy-cli.

The problem is because of multiple versions of Ruby / Rubygems. Check the content of which gem, which heroku and which taps. You may find some are running on 1.8 and some on 1.9. The gems won't be available to each other.

I'm on an Ubuntu system and my solution was:
Remove every trace of ruby1.8 and 1.9.1 (the bin scripts refer to specific versions so I wanted to start clean).
sudo apt-get install ruby1.9.1-dev
sudo apt-get install heroku-toolbelt
then vim which gem reveals it's running 1.9.1. No more conflicts
sudo gem install taps

Alternatively, if you want to keep 1.8, try this: sudo gem1.9.1 install taps (depends on your system and environment, if you have gem1.9.1 in bin.)

from legacy-cli.

Just getting taps to install was a pain (sudo aptitude install irb ruby rubygems ruby-dev; sudo gem install taps). It's not working for me with these versions:

$ heroku --version
2.24.0

$ taps version
0.3.23

$ ruby --version
ruby 1.8.7 (2010-01-10 patchlevel 249) [i486-linux]

from legacy-cli.

@aidanlister - Are you seeing the same load error as others? Does gem list taps list taps of the version listed here? Sorry to not offer a direct solution but I haven't had luck directly reproducing this.

from legacy-cli.

Did you take a look at my post above? Check how many versions of ruby you have.

from legacy-cli.

I've updated to ruby1.9 (sudo aptitude install irb1.9 ruby1.9 rubygems1.9 ruby1.9-dev) and I've uninstalled ruby1.8, then ran sudo gem install taps again. Still no luck.

This does appear to be a ruby problem on Ubuntu 11.04 ... it's easily replicable, just download the virtualbox and try the above steps: http://vagrantup.com/docs/getting-started/index.html

$ gem list taps
*** LOCAL GEMS ***
taps (0.3.23)

All versions of heroku, irb, gems point to ruby1.9 and a find / -name ruby shows no other versions floating around.

from legacy-cli.

@aidanlister - I ran through things with vagrant and the lucid32 box, went something like this:

$ sudo gem install heroku
$ sudo apt-get install libsqlite3-dev
$ sudo gem install taps
$ heroku db:pull
Loaded Taps v0.3.23
 !    Invalid database url

Same as I get on my mac. In both cases it seems to not be encountering the "Unable to load" error. Thoughts on what I may have missed or done differently? Any help reproducing this so we can get to the bottom of it would be greatly appreciated. Thanks!

from legacy-cli.

Same issue as the guys above.

from legacy-cli.

I also installed Heroku from the tool belt:

bundle install

rbenv rehash

heroku db:pull
 !    Taps Load Error: no such file to load -- taps/operation
 !    You may need to install or update the taps gem to use db commands.
 !    On most systems this will be:
 !    
 !    sudo gem install taps

gem list taps
*** LOCAL GEMS ***
taps (0.3.23)

heroku version
heroku-gem/2.20.1

taps version
0.3.23

which heroku
/usr/bin/heroku

which taps
/Users/me/.rbenv/shims/taps

gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.8.10
  - RUBY VERSION: 1.9.2 (2011-07-09 patchlevel 290) [x86_64-darwin11.2.0]
  - INSTALLATION DIRECTORY: /Users/me/.rbenv/versions/1.9.2-p290/gemsets/mygemset
  - RUBY EXECUTABLE: /Users/me/.rbenv/versions/1.9.2-p290/bin/ruby
  - EXECUTABLE DIRECTORY: /Users/me/.rbenv/versions/1.9.2-p290/gemsets/mygemset/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86_64-darwin-11
  - GEM PATHS:
     - /Users/me/.rbenv/versions/1.9.2-p290/gemsets/mygemset
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://rubygems.org/

from legacy-cli.

@michrome - thanks for the detailed report. Sounds like one of my colleagues has reproduced the issue and is working toward a solution. I gather it has to do with the isolated version of things from the toolbelt not being able to find things somehow, but the toolbelt isn't really my area of expertise. We hope to get a fix out soon though.

from legacy-cli.

Any progress on this? Completely unable to pull.

% heroku version
2.25.0
% gem list taps
*** LOCAL GEMS ***

taps (0.3.24)

from legacy-cli.

@tim-vfiles - are you using the toolbelt in conjunction with rbenv? That was the set of conditions within which my coworker saw it specifically. I've never reproduced it successfully on my own machine though. Also, what version of Ruby are you using and what operating system?

from legacy-cli.

Sorry, should've provided more info, had a fw different similar issues open in tabs and might've chosen the wrong one.

I'm using 1.9.3-p194 managed by RVM on Kubuntu 12.10. The taps and heroku used are above, though I've tried rolling back as suggested. Still getting the error about taps/operation.

from legacy-cli.

@tim-vfiles - are you using a gem-installed version of heroku or toolbelt?

from legacy-cli.

Originally tried the toolbelt, then the gem which I still have. No difference between the two as far as I can tell.

from legacy-cli.

@tim-vfiles - I would recommend trying pgbackups instead. They are a better solution than taps in many cases anyway if you can manage it. There is detailed info here: https://devcenter.heroku.com/articles/pgbackups Hopefully that can get you what you need in a less troublesome way.

from legacy-cli.

I have the same problem.

I’m on Mac OS X 10.7.4. My app was built with Refinery CMS 2.0.4 on Rails 3.2.4, and I have since upgraded to Refinery CMS 2.0.5. I want to use taps to transfer the CMS pages I’ve created locally to Heroku. My local database is MySQL. I installed heroku from the Toolbelt.

bundle install

rbenv rehash

heroku db:push
 !    Taps Load Error: no such file to load -- taps/operation
 !    You may need to install or update the taps gem to use db commands.
 !    On most systems this will be:
 !    
 !    sudo gem install taps

gem list taps

*** LOCAL GEMS ***

taps (0.3.24)

heroku version
2.26.6

taps version
0.3.24

which heroku
/usr/bin/heroku

which taps
/Users/roryokane/.rbenv/shims/taps

gem env
RubyGems Environment:
  - RUBYGEMS VERSION: 1.8.23
  - RUBY VERSION: 1.9.3 (2012-04-20 patchlevel 194) [x86_64-darwin11.3.0]
  - INSTALLATION DIRECTORY: /Users/roryokane/.rbenv/versions/1.9.3-p194/lib/ruby/gems/1.9.1
  - RUBY EXECUTABLE: /Users/roryokane/.rbenv/versions/1.9.3-p194/bin/ruby
  - EXECUTABLE DIRECTORY: /Users/roryokane/.rbenv/versions/1.9.3-p194/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86_64-darwin-11
  - GEM PATHS:
     - /Users/roryokane/.rbenv/versions/1.9.3-p194/lib/ruby/gems/1.9.1
     - /Users/roryokane/.gem/ruby/1.9.1
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://rubygems.org/

rbenv version
1.9.3-p194 (set by /Users/roryokane/<path-to-project>/.rbenv-version)

The first time I ran heroku db:push after installing taps, I had forgotten to run rbenv rehash. Could that have messed something up?

from legacy-cli.

See Issue #188 – maybe it’s related.

from legacy-cli.

@roryokane Could be. I'm not really sure why this seems to break for only a subset of people but I'm sorry you ran into it. You can use the gem version, instead of toolbelt, as a work around. I think you can just delete ~/.heroku/client if it exists and then do gem install heroku and after that you'll be on the gem. That should avoid the issue you saw (which is due to toolbelt using vendored gems). Let me know if you are still stuck though and I can try to figure something else out for you. Thanks!

from legacy-cli.

Not to add confusion, but for what it's worth:

What worked for me was to _un_install the gem (all versions, if there's multiple), make sure I'm using the CLI, execute for the first time.

The gems get reinstalled by bundler and override the CLI (which heroku points to the gem), but it seems to continue working anyways without this error.

Don't ask me...

from legacy-cli.

@tim-vfiles - fair enough. Thanks for the update, load paths are definitely a pain in the butt some times. Glad to hear people have found good work arounds since I have had a heck of a time reproducing these issues consistently.

from legacy-cli.

@geemus Thanks. A simple gem install heroku, and a rbenv rehash to be sure, fixed it for me. heroku db:push now works.

from legacy-cli.

I got this too (I'm using rvm), and simply adding taps to my Gemfile and bundle exec-ing the heroku pull command fixed it for me. Brute force solution, but it works.

from legacy-cli.

@kaiwren - glad you found a fix and thanks for sharing it with us.

from legacy-cli.

@roryokane Check the --content-- of which heroku and which gem, not just the path of the file being run.

The file should have a hash bang as first line and it says which version of gem it's running. If it's not the same version as for heroku, e.g. heroku runs on 1.9.1 and gem on 1.8, you might need to run gem1.9.1 install taps for heroku to work.

from legacy-cli.

@lewisdiamond Thanks for clarifying, but I have already solved my issue. However, I had indeed misunderstood what you meant by “content” in your first comment, so your comment might help others, if my or kaiwren’s solution doesn’t work for them.

from legacy-cli.

Thanks guys for sharing what has worked well for you. I'm still trying to learn all tho moving parts and taps is one that I still have little to no experience in, which unfortunately has made it hard to be helpful on this stuff.

from legacy-cli.

Just as an update to anyone who still may be encountering this, there seems to be an incompatibility with toolbelt, at least in some cases, such that your best bet may be to gem install heroku and try again.

from legacy-cli.

FYI - I just encountered this error. In my case, I wasn't using toolbelt at all, and I had the latest versions of both heroku and taps. My problem was that I was in a project directory that included "heroku" in the Gemfile but not "taps". Running heroku from the command line was using the bundled version (even though I did not say bundle exec), and since taps did not exist in the bundle, it was invisible to the heroku gem.

Solution: Add gem 'taps' to my Gemfile

from legacy-cli.

@adamlogic - thanks for the details, totally makes sense that it could occur this way (but slipped my mind to mention it).

from legacy-cli.

I'm going to call this good for the time being, but if you are still experiencing this and the gem and/or Gemfile usage mentioned here doesn't fix it for you please let me know.

from legacy-cli.

My gem version is as follow:

heroku (2.30.2)
heroku-api (0.3.2)
taps (0.3.23) (Even try with version 0.3.24)

And in had the same issue here. Tried the above solutions, none of them work.

I'm not using rvm.

from legacy-cli.

@datnt - are you using a toolbelt installation or a gem installation of heroku?

from legacy-cli.

I solved problem by using
rvm reinstall 1.9.2
bundle install

than install all gems which you need without sudo.

gem install heroku

and now
heroku db:push works for me! Great!

My Gemfile

source 'http://rubygems.org'

gem 'rails', '3.1.3'

Bundle edge Rails instead:

gem 'rails', :git => 'git://github.com/rails/rails.git'

group :development, :test do
gem 'sqlite3'
end
group :production do
gem 'pg'
end
gem 'taps'
gem 'json'
gem "multi_json", "~> 1.3.6"

Gems used only for assets and not required

in production environments by default.

group :assets do
gem 'sass-rails', '> 3.1.5'
gem 'coffee-rails', '> 3.1.1'
gem 'uglifier', '>= 1.0.3'
end

gem 'jquery-rails'

from legacy-cli.

@finfort - great, thanks for the update.

from legacy-cli.

@finfort's solution finally worked for me after all else failed

from legacy-cli.

I'm still having this issue.

Using heroku-toolbelt/2.33.0 and gem list shows taps (0.3.24). Running heroku db:pull results in the same Taps Load Error: no such file to load -- taps/operation. I'm using rbenv and doing taps alone on the command line works fine.

I should note that we've started using the toolbelt version exclusively now that the gemified version has been deprecated.

from legacy-cli.

I was having this same problem with Rbenv (with Ruby !.9.3-p125) and the toolbelt.

I gave up trying to work with the toolbelt, so I added 'heroku', 'sqlite3', and 'taps' to my Gemfile and have been successfully been using bundle exec heroku db:pull.

from legacy-cli.

@dpmccabe Yup that's what I ended up doing. Which is fine except the gem versions is being deprecated and we're being told to use the toolbelt.

from legacy-cli.

adding both heroku and taps in gemfile and then doing bundle exec heroku db:pull fixed it form me.

from legacy-cli.

This issue is still happening for me. All combinations of:

• system gem install
• rbenv install with 1.9.2 and 1.9.3
• adding to Gemfile and bundle exec heroku
• heroku toolbelt

Nothing working. THis issue needs to be reopened.

from legacy-cli.

I'm experiencing this as well.

$ heroku version
heroku-toolbelt/2.33.2 (x86_64-darwin10.8.0) ruby/1.9.3`

$ taps version
0.3.24

@geemus If you want to pair on this, email me and set up a time and we can use my machine for you to track it down.

from legacy-cli.

@wesgarrison @HuffMoody - sorry to hear that. Could you perhaps try using - https://github.com/heroku/heroku-taps (which includes vendored taps). I haven't touched it in a little while but I think it might help and be the quickest/easiest fix.

@wesgarrison - sounds good. I'm travelling today, but if the above doesn't work for you I should be able to work on it more directly later this week.

from legacy-cli.

@geemus I used pgbackups to get my database loaded, so I'm not in a bind to get this done, so I can wait until you're around and available to dig in without mucking things up in the meantime.

from legacy-cli.

@geemus I'm using pgbackups as well so no immediate rush. Installing heroku-taps then using db:pull gives the following error

 !    Heroku client internal error.
 !    Search for help at: https://help.heroku.com
 !    Or report a bug at: https://github.com/heroku/heroku/issues/new

    Error:       uninitialized constant Heroku::API (NameError)
    Backtrace:   /usr/local/heroku/lib/heroku/command.rb:213:in `rescue in run'
                 /usr/local/heroku/lib/heroku/command.rb:259:in `run'
                 /usr/local/heroku/lib/heroku/cli.rb:28:in `start'
                 /usr/local/heroku/bin/heroku:24:in `<main>'

    Command:     heroku db:pull --confirm noirblancostaging --remote staging
    Plugins:     heroku-taps
    Version:     heroku-toolbelt/2.33.2 (x86_64-darwin10.8.0) ruby/1.9.3

from legacy-cli.

@HuffMoody I'm seeing the same thing right now too.

from legacy-cli.

Well, crap. I'm home again so my schedule is less hectic, hopefully a solution can happen soon. As someone who has never personally used taps, what things are you guys needing/wanting from it that pgbackups can't support? (pgbackups in the more recommended path these days, fwiw).

from legacy-cli.

The main thing is cross database support. Sometimes I want to push a mysql db into heroku/pg. Or, I only want to push a single table, which I might be able to do with pgbackups, but I'm not sure and don't see any documentation on how to do that.

With pgbackups you have to be running pg locally. Maybe I should do that conversion locally, but it's one more step.

Could be that pgbackups could replace the taps interface with better documentation, but other might have more stringent usecases than me.

from legacy-cli.

@will - is there a way to use pgbackups to do single table transfer or is it always full-db?

@wesgarrison - thanks for clarification. I would argue that cross database is to be avoided (there are tons of weird gotchas that taps can't really deal with in a reasonable way, which you might not run into yet, but likely will if you use this a lot). Is there a reason not to run pg locally in the first place (and therefore avoid ever needing to convert the data)? The single table case is interesting though and certainly not clear how (or at least I don't know how). Are there particular parts of pgbackups that you feel need additional docs or that you have questions about?

from legacy-cli.

pgbackups is always full db. If you need to do a single table, you can run pg_dump from your local machine against a remote heroku postgres database.

Also taps is awful, I cant wait until we kill it. It's the worst. It is so bad.

from legacy-cli.

IMO, then, I say deprecate taps and replace with links to good documentation examples on how you'd do the equivalent things in pgbackups. It works in the gem, so don't support it in toolbelt, perhaps.

Someone can always use taps locally to convert their local mysql/sqlite/whatever database into a local pg database (which is where that should probably happen anyway so it can be reviewed) and then up into heroku.

from legacy-cli.

@wesgarrison - yeah. I think we want something like that to happen internally but nobody is focusing on it presently.

from legacy-cli.

gem install heroku and then bundle install worked for me thank you @geemus

from legacy-cli.

I'm getting this error too. Here's my taps and heroku version info:

> heroku version
heroku-toolbelt/2.39.2 (x86_64-darwin10.8.0) ruby/1.9.3
> taps version
0.3.24

from legacy-cli.

For me installing the toolbelt and sqlite3 via homebrew fixed the issue. ruby 1.9.2

from legacy-cli.

I too am getting this error, and here's how I worked around it (on Mac OS X 10.8) with rbenv as my Ruby manager

Fire up your favorite editor and open /usr/local/heroku/bin/heroku. There on line one, you'll see that the script is set to use a bundled version of Ruby:
#!/usr/local/heroku/ruby/bin/ruby

I can't explain why Heroku bundles a Ruby version with the toolbelt, but I can tell you that's why changing Ruby versions with rbenv has no effect on this problem.

Since I use Ruby 1.9.3 for pretty much all of my projects anyway, I went ahead and edited that like at the top of the heroku script to read:
#!/usr/bin/env ruby

That uses the equivalent of which ruby to determine which ruby to use to run this script. Saved off the file and bam! worked like a charm.

from legacy-cli.

I can confirm @jcarlson 's work-around on OS X 10.8.4.

from legacy-cli.

Taps, db:push and db:pull are soon to be replaced with pg:push and pg:pull.

If anyone subscribed to this thread would like to check it out early and give feedback, information is at heroku/heroku-pg-extras#42

Even though this issue here is closed, it comes up on google results for "heroku pg:pull", and seems like people are still discussing here about taps.

from legacy-cli.