Open tsmith023 opened 1 month ago
Currently if a RuntimeError("Event loop is closed") is raised, the user observes a potentially cryptic error and stacktrace. We should instead catch and re-raise such an exception with a better description to improve the UX
RuntimeError("Event loop is closed")
I would like to take on this issue if it's available.
Currently if a
RuntimeError("Event loop is closed")
is raised, the user observes a potentially cryptic error and stacktrace. We should instead catch and re-raise such an exception with a better description to improve the UX