I've just updated our Slack dependency, so hopefully that fixes the issue. It seems they've improved their error handling in reading from the WebSocket. If the same error crops up again I'll have to resort to some form of the recover solution I has before.
Fixes #60
I've just updated our Slack dependency, so hopefully that fixes the issue. It seems they've improved their error handling in reading from the WebSocket. If the same error crops up again I'll have to resort to some form of the
recover
solution I has before.