When error handling in akka streams - is there some common pattern for bubbling errors to a “host” Actor?
Materializing some Future[Done] from somewhere in the graph and watching it is somewhat misleading, since errors upstream (or “sidestream”) to it are invisible.
Materializing all the values often leads to 10+ futures that you have to mess around with.
Since the materializer’s decider sees the exception, is it a good idea to message the host Actor with the result from there? seems somewhat unnatural.
Is there another way to handle these sorts of issues?
Side note: whenever possible, of course encoding errors in types (Either/Try) to handle errors on the application-level is great, I’m referring to cases where errors are out of my control, aka library users or external components.