-
-
Notifications
You must be signed in to change notification settings - Fork 135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exceptions within .on()
blocks are mysteriously ignored
#396
Comments
I believe it's ruby-concurrency/concurrent-ruby#634 but I never had time to work on it. |
route
added a commit
that referenced
this issue
Jan 4, 2024
We can easily workaround async with queue and a thread and btw simplify the subscriber. Swallowing errors is not good, closes #396
route
added a commit
that referenced
this issue
Jan 4, 2024
We can easily workaround async with queue and a thread and btw simplify the subscriber. Swallowing errors is not good, closes #396
route
added a commit
that referenced
this issue
Jan 4, 2024
We can easily workaround async with queue and a thread and btw simplify the subscriber. Swallowing errors is not good, closes #396
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I noticed that exceptions raised within
.on()
blocks are mysterious ignored, and not even logged. This makes debugging errors within other code that's called within.on()
blocks very difficult.Example Code
Expected Result
An uncaught exception being raised.
Actual Result
Nothing
Version Information
The text was updated successfully, but these errors were encountered: