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
observe must be guarded against subject/cleanup throwing #4
Comments
The problem is the unsubscribe function throws, and Intended or not : good question. The current behavior is obviously confusing, but at the time the unsubscribe function is called the process is already terminated (successfully). At first glance I'd say the whole process should fail, because proper cleanup of resources is part of the job. |
Post-hammock thoughts : no ambiguity here. Both |
Interesting, I now understand that the problem is cancelled because a Thread Death is thrown by unsubscribe. Wouldn't this example still have to print "err" ... |
I acknowledge that swallowed errors is a source of frustration for users. The purpose of Now if you need to be sure your (defn show-error [flow]
(m/ap (try (m/?? flow)
(catch Throwable e
(prn e)
(throw e))))) Then you could insert this just before I considered two alternatives :
|
In the following experiment,
(inst)
canceller at any time results in immediate aggregate printing and cancellation being effectiveThe text was updated successfully, but these errors were encountered: