If I throw an exception from inside a fiber, there is an issue with redundant logging. I expect the framework to just surface the exception by rethrowing it at the point where I started or resumed this fiber, which it does, but it also runs the Fiber.defaultExceptionHandler ... twice. This results in stderr spam. I'd rather it printed nothing at all and let the exception propagate out of the fiber like any other.