The overlay only displays the exception message and the cljs line where it happened, but not the full clj stack trace; and given this expands using &env it's non-trivial to reproduce in pure clj