commit 362beadda2797ff6878af8c3b232b7b4e41b2141 Author: Jacob Van De Weert Date: Wed Oct 3 18:13:16 2018 -0400 have rogue catch MongoInterruptExceptions and add details (#9178) This adds a more detailed error message with some additional context and the current thread name to help with debuggging, so hopefully the next person to hit this won't have to spend two months tracking down the root cause. As mentioned in the comment, there are some shenanigans happening here with string manipulations to generate this error message. This was mostly motivated by me not wanting to stick a 200 character line in this file, but I claim it's also slightly more efficient than any of the less custom ways this could have been written. And at least it's quarantined to its own helper function. This commit also adds some basic tests for the twitter Future callbacks, and the new exception encoding. (sapling split of c402958f499dfc1fd025911cc22c51e8a0003e36) .../twitter/TwitterFutureMongoCallback.scala | 37 ++++++++++++++++++++-- 1 file changed, 35 insertions(+), 2 deletions(-) commit 4aa6650f859c8e3087dcbbf46171775a1a0deead Author: Ian Tabolt Date: Fri Jun 15 17:56:01 2018 -0400 Scalafmt EVERYTHING (#6987) * Run scalafmt on everything * Flip the switch to enable scalafmt (FSQ_ENABLE_SCALAFMT=True) * Add some // format: off and // format: on comments in particularly weird cases * Disable scalafmt on files that cause exceptions (sapling split of 61c9ef3975aa4f55f70e479d7908f42de0685d26) (sapling split of 8264ffd5eb789041b44688c92b468f426833730e) .../fsq/rogue/adapter/callback/twitter/TwitterFutureMongoCallback.scala | 1 - 1 file changed, 1 deletion(-)