Eaden McKee

I have this issue and I'm not using email_spec.. maybe it's because of devise ( the email is a devise email ) gemfile ``` source 'https://rubygems.org' gem 'unicorn' gem 'rails',...

cloning the dokku/docker-wait repo, and running `docker build . -t dokku/wait:0.4.3` worked for me to resolve the issue. What should the image version used on dokku-postgres be changed to? 'latest'...

https://github.com/eadz/double_entry/pull/6 That branch passes, so there isn't any test coverage to help explain it. There also isn't any git history on the locking file to help us :/ https://github.com/envato/double_entry/commits/master/lib/double_entry/locking.rb In...

DoubleEntry doesn't prevent deadlocks from within the lock accounts block. You could do ``` ruby DoubleEntry.lock_accounts(*accounts) do @user.lock @product.lock end ``` in one place and ``` ruby DoubleEntry.lock_accounts(*accounts) do @product.lock...

> > Maybe there is a way to improve this API? > > I don't think there is a way to improve the locking without either a) changing ActiveRecord's behaviour,...

@notahat I'm not saying do away with account balance records, or per-account locking, I'm saying the really complicated "ensure outermost transaction" locking code is due to the _creation_ of account...

> @eadz: There's definitely a lot of complexity in there to support lazy creation of account balances. And yes, you could simplify things if you assumed all account balances were...

> If you get a deadlock in a nested transaction, ActiveRecord behaves as though just the inner transaction is being rolled back, but MySQL rolls back the outermost transaction. Makes...

`What about a :retry_on_deadlock => false or allow_outer_transaction => true option?` I think we definitely need some more options. I think there were some decisions made early on that have...

@kschutt for most cases, you wouldn't want to eliminate locking. I guess in theory you could rely on a line check but I don't believe it will fix any error...