maelstrom icon indicating copy to clipboard operation
maelstrom copied to clipboard

Make client process exit more aggressively on signal

Open bobbobbio opened this issue 8 months ago • 0 comments

Right now if the client-process gets a signal after the local worker has started, it fails the client state machine. This only causes the process to exit indirectly by making the connected client get a fatal error and hopefully it closes its connection.

This is still a desirable property so that the client can observe the error, but if the client isn't behaving properly we should probably time-out and exit the process. Potentially we could do this whenever we enter an error state, we don't need to hang around waiting for the client to observe the error forever probably.

bobbobbio avatar Jun 23 '24 22:06 bobbobbio