Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Regular disconnect / reconnect #117

Open
mooomooo opened this issue Jul 2, 2020 · 4 comments
Open

Regular disconnect / reconnect #117

mooomooo opened this issue Jul 2, 2020 · 4 comments

Comments

@mooomooo
Copy link

mooomooo commented Jul 2, 2020

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?

@dylex
Copy link
Owner

dylex commented Jul 10, 2020

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.

@mooomooo
Copy link
Author

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)

@mooomooo
Copy link
Author

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.

@sairuk
Copy link

sairuk commented Aug 22, 2021

Same problem as op, triggers notifications everytime the reconnect triggers. be nice to see these handled

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants