Again, I worry we're throwing away essential information (e.g. the line number in DynamicClusterImpl where the exception originated).

Also, I worry that if we ever propagate the unwrapped exception rather than the real exception, then it'll look like it was thrown in the current thread - which would be very bad! Especially if it's something like an InterruptedException!