Description
When Await.result throws an exception which originated from a different thread, the resulting stacktrace doesn't include the path leading to the Await.result() call itself, making it difficult to identify the impact of these exceptions. For example, I've seen cases where broadcast cleaning errors propagate to the main thread and crash it but the resulting stacktrace doesn't include any of the main thread's code, making it difficult to pinpoint which exception crashed that thread.