Are you doing anything funky to transactions? You're not trying to use database_cleaner or anything, right?
-
That's the prob. A fresh 5.1 app has same transaction object_id in test and view, but our app has different between test and view.
Right, so the thing is to figure out what's different in your app and add that to the repro
-
-
Turns out puma was booting in cluster model causing it to created a uniq connection pool based on the fact that the PID was different.
-
Is that something we can easily detect/error on?
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.