Open LourensVeen opened 1 year ago
I've improved this a little bit, but it relies on looking for a string in the error log, which is a hack. It does work though, and it makes your life a lot easier, so we'll take it for now, but this issue remains open.
If a connection to a peer is lost then the component raises and exception and crashes, which causes the manager to treat it as crashed, even though there's nothing wrong with that component. That can lead to confusion when debugging the problem.
Potential solutions:
There's a potential issue here with accumulator components, which need to catch that exception when receiving on S, then send on O_F and shut down cleanly. Of course, accumulator components don't really exist yet other than in my head.