Invalid database url when trying to db:pull about legacy-cli HOT 6 CLOSED

I've been having the same issue. Thanks to the poster, I was able to downgrade my Heroku gem to 1.13.6 and everything's working again! Thank you! This is definitely a critical bug :/ db:pull-ing to a local sqlite database file is very common, as far as I know

from legacy-cli.

Thanks for your comment, I think it's kind of a critical bug, I'm very scared that so few people reported it.

I could do a pull-request to fix it, but I'm beginning to be a little bored with this gem, I've already made a pull-request 3 weeks ago (#32) and it's still not merged.

I'm very disappointed that on one hand the Heroku service works pretty well, and on the other hand the gem and its development is so slow and strange (ddolar told me that my pull-request should be merged, then closed it, but didn't merged it yet...)

Sorry if I'm rude, but it's a shame that a bug as critical as this one could've been introduced without being fixed (7 new releases since I reported this bug, and still no reply from the maintainer).

Fuck it, really, I don't get it.

from legacy-cli.

@rymai I pinged Heroku and they're "aware of the issue, and
working on resolving it."

I can't comment on why they haven't commented on this issue or marked it with any tags. I understand that they are insanely busy, but I hope they find the time to comment on issues.

As a sidenote, they pointed out that Taps is NOT recommended for real backups, and you should checkout the pgbackups addon: http://addons.heroku.com/pgbackups

That said, we both ran into this issue because Taps is crazy convenient :)

from legacy-cli.

Introducing a bug preventing from using Taps is not a way to recommend people not to use it.

Moreover, it's bullshit to say that they're "aware of the issue, and working on resolving it." when it's been introduced on November 17, 2010, and still not fixed.
It's been only 18 days and 7 releases since then, after all! :)

My advice to Heroku: you should be honest, if you say you're working on it, work on it, if not, don't say it just to make us happy, I don't care. If you don't work on it, I can fix it myself and pull-request you the fix, but at least, actually pull-request it.

In the end, I think I'm gonna stop wasting my time and use pgbackup since it's recommended AND it's the only given option that can work in my case. ;)

from legacy-cli.

Solved in d69239f

from legacy-cli.

Ah! It should work better now, thanks!! ;)

from legacy-cli.