]> cat aescling's git repositories - mastodon.git/commit
Try fixing ThreadResolveWorker calls (#3599)
authorThibG <thib@sitedethib.com>
Mon, 5 Jun 2017 22:09:14 +0000 (00:09 +0200)
committerEugen Rochko <eugen@zeonfederated.com>
Mon, 5 Jun 2017 22:09:14 +0000 (00:09 +0200)
commit7adac1bc51d76fde4df51f4f3d18cf39b01516a4
tree32b88f16e87b3a3cba89511acbf9760e7843065d
parente859d6f259cfe4aa61c2e68a18db95d34d460b81
Try fixing ThreadResolveWorker calls (#3599)

* Try fixing ThreadResolveWorker calls

From my understanding of ActiveRecord, a transaction is commited as soon as
the exit of the outmost ActiveRecord.transaction block. However, inner
transaction blocks will exit without the transaction being commited.

In this case, ThreadResolveWorker were fired *within* a transaction block,
so moving the call out of it should do the trick. However, this is somewhat
fragile, as this whole codepath could be called within yet another transaction.

* Set status thread within the transaction block if it is immediately available from database
app/services/process_feed_service.rb