-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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
Unhandled errors go to UncaughtExceptionHandler #1766
Conversation
Rather than swallowing/logging errors, ScheduledAction now delivers them to the UncaughtExceptionHandler for the executing Thread. This gives client applications control over the handling of errors that occur off of the calling Thread.
Thank you @loganj |
Oops, forgot to reference the original issue: #1682 |
Unhandled errors go to UncaughtExceptionHandler
I haven't had a chance to test yet, but without |
Pretty sure ThreadGroup has us covered.
|
Ah nice. That's exactly what I'd want it to do. I'll play to confirm. Thanks @loganj for helping out with this. |
Confirmed. It works perfectly. public static void main(String[] args) throws Exception {
Observable.interval(100, TimeUnit.MILLISECONDS).map(i -> {
throw new RuntimeException("fail!");
}).subscribe();
Thread.sleep(100000);
} outputs to terminal
|
Rather than swallowing/logging errors, ScheduledAction now delivers them
to the UncaughtExceptionHandler for the executing Thread. This gives
client applications control over the handling of errors that occur off
of the calling Thread.