slack-libpurple
slack-libpurple copied to clipboard
dylex
Regular disconnect / reconnect
Every ~8 hours, the plugin disconnects and reconnects, spamming my bitlbee control channel with the following messages:
@root | slack - Error: Connection closed
@root | slack - Signing off..
@root | slack - Reconnecting in 5 seconds..
@root | slack - Logging in: Looking up team
@root | slack - Logging in: Finding user
@root | slack - Logging in: Logging in
@root | slack - Logging in: Requesting RTM
@root | slack - Logging in: Connecting to RTM
@root | slack - Logging in: RTM Connected
@root | slack - Logging in: Loading Users
@root | slack - Logging in: Loading conversations
@root | slack - Logging in: Logged in
Is there a way to diagnose (then prevent) these drops, or if not at least suppress these messages?
From what I've seen, these disconnects are initiated by slack itself -- the plugin tries hard to keep connections open. It might be theoretically possible for the plugin to handle reconnects itself, but it creates tricky windows where messages have to be queued somehow. As for suppressing the messages, those look like the connection steps (normally shown as a progress bar in pidgin), so that sounds like a bitlbee question.
Ah I see. The main consequence of this though is that it seems to lose the reference for multi-user group DMs after a reconnect. (This may be a bitlbee issue too, I don't know)
Just updating my previous comment, it seems as though all open chats (DMs, joined channels, etc) lose their identities after such a reconnect. A new message from anyone else in that chat re-establishes the connection, but until then, messages sent to that chat disappear into the aether.
Same problem as op, triggers notifications everytime the reconnect triggers. be nice to see these handled
