Results 50 comments of Max Melentiev

@dplummer have you turned your redis server down? You can just provide `port: 6380` (or other one that is not listened by redis) in my oneliner.

Sorry, i think i can get you wrong. Do you mean 'nope, no failures when server is down' or 'nope, did not turned server down'? I just tried with same...

@pietern, @dplummer here is my backtrace (here I tried in new environment): ``` $ irb 2.1.1 :003 > require 'redis' => true 2.1.1 :004 > require 'hiredis' => true 2.1.1...

Thanks for the explanation! I've noticed that Rails.cache adapter for redis rescues only from Errno::ECONNREFUSED, Redis::CannotConnectError. So it will fail when cache server is down.

I have pick some code from db_charmer and modified it for sdbp. But `get_connection_name` should be fixed. I couldn't find easy way to get proper connection name for now. You...

Seems like it's fixed in https://github.com/prontolabs/pronto/commit/005ca38e0443d1afcd7d45793cd9ac46400aeea2

@kirs this is good approach. Though `db:rollback` can be useful in staging and testing environments.

> Unsure what migration rake db:rollback would rollback. The latest successful. `STEP` envvar can be passsed to rake from cap to rollback more migrations.

`module_function` does not work with `attr_accessor`, visibility modifiers and methods which define new ones (ex, ActiveSupport's `Module#delegate`). So `module_function` is useful only for very simple cases, while `extend self` provides...

Hi, and thank you for the contribution! Is it possible to pass credentials like `HTTP_PROXY=http://username_for_proxy:[email protected]:5678`?