Closed lexaknyazev closed 5 years ago
The LoadBalancer
is not necessarily based on IsolateRunner
runners. The Runner
API does not have a way to register unhandled asynchronous errors.
Perhaps it would make sense for the default IsolateRunner
used in a LoadBalancer
to expose uncaught errors to the current zone of the request, but I don't think the LoadBalancer
API is the right place to do something that doesn't work for any runner.
I don't think the
LoadBalancer
API is the right place to do something that doesn't work for any runner.
Okay, that makes sense.
the default
IsolateRunner
used in aLoadBalancer
What does it mean? A LoadBalancer
is created with a pre-existing collection of Runners (default constructor) of with a generator (static Future<LoadBalancer> create()
).
True, I actually thought there was a default, but there isn't.
With single
IsolateRunner
, it's possible to get aStream
of unhandled errors:It would be nice for
LoadBalancer
to provide a combinedStream
of unhandled errors from all spawned runners, or a public API to access eachrunner.errors
from outside.