The slack client thread will eventually exit, not seemingly due to any particular event, usually within 12-24 hours of being launched. Not a crash fault, but at the same time unclear why the TLS read is failing.
This should be investigated and fixed; alternately there should be logic (optionally enabled) to detect this sort of thing and automatically reconnect so applications do not need to be aware of this.
[2024-08-24 00:13:06] slack-rtm.c:400 slack_parse_message(): Event channel_updated not currently handled: REDACTED...
[2024-08-24 00:15:19] slack-client.c:133 __ssl_read(): SSL: SSL_ERROR_ZERO_RETURN
[2024-08-24 00:15:19] slack-client.c:638 slack_read(): Failed to read WebSocket frame
[2024-08-24 00:15:19] Event loop exiting
[2024-08-24 00:15:19] Event loop has ended
You must be
10/17/2024 6:41 PM — InterLinked
Autoresolved by code commit on GitHub:
example-common.c: Set autoreconnect flag before connecting.
https://github.com/InterLinked1/slack-rtm/commit/db4aa57b8abb3eb06e2cde07d5a27421c3280832