Use of unified error handler about aeron-go HOT 6 CLOSED

@lirm just curious how you imagine the unified error handler working in go. I'd be happy to work on this: your port just saved us tons of time (we were planning on starting on one ourselves).

from aeron-go.

@iamthebot Just now realized I've missed your comment. :(

My thinking was to pass a single error channel from the top level calls, but no deeper than conductor. Although, I've later realized that it's likely to be replaced by error logbuffer. Short term - using error channel for consolidated error reporting would be extremely helpful.

from aeron-go.

@lirm would errors from lower level calls be propagated up to the consolidated error channel? If so, that's not an insignificant change given that the error logbuffer is ultimately going to be the way to go.

from aeron-go.

Agreed. I've created this issue back when I was listing out what's missing, so given that most other parts of functionality are there, this may be an irrelevant one.

from aeron-go.

In that case close this issue @lirm ?

from aeron-go.

Good point

from aeron-go.