Maciej Szajna

You seem to be defending the pattern with handlers catching and raising callback exceptions pretty strongly. Does that mean you consider it to always have been a part of the...

>>You seem to be defending the pattern with handlers catching and raising callback exceptions pretty strongly. Does that mean you consider it to always have been a part of the...

> The problem occurs under the following circumstances: > 1. Asynchronous handlers are used. > 2. An exception is thrown by respond or raise outside the calling thread. > 3....

Let me elaborate this a bit: The problem is that lacinia's use of `future` (per link above) prevents the application from leveraging `Thread/setDefaultUncaughtExceptionHandler` (see Stuart Sierra's blog post https://stuartsierra.com/2015/05/27/clojure-uncaught-exceptions). Any...

> essentially I'd prefer to capture the exception in the future's thread, and re-throw the exception when derefing the future In this instance, `future` is never returned to the caller,...

ds4drv seams to be creating a device for each configured controller at startup ("Created device /dev/...") but if you configure just one and try to connect another controller later on...