Bug #115
sconnect on protocol error
| Status: | Closed | Start: | 2009-05-11 | |
|---|---|---|---|---|
| Priority: | High | Due date: | 2009-07-08 | |
| Assigned to: | % Done: | 100% |
||
| Category: | IRC protocol | Spent time: | 0.50 hour | |
| Target version: | 1.0 | |||
| libpurple: |
Description
I'm using purple facebook plugin.
Sometimes I get:
20:56 [minbif] !##### [WARNING] [facebook] fatal connection error
20:56 [minbif] !##### *** Notice -- Error(####@####:bigbrownchunx-facebookim0): Server closed the connection.
I don't really know where the problem is, nearly sure it's on plugin's side.
After that, I can /sconnect to re-enable the connection.
A quick & dirty fix would be to autoreconnect accounts on disconnect, when the disconnect is not intentional, should it be possible?
This may be usefull for some other buggy plugins, too ;)
Associated revisions
Revision d7b7d1cf925018e5bd38cc0c27286f5938c951bd
auto-reconnect when disconnected by server (incremental delay)
Closes #115
History
Updated by pankkake - 10 months ago
Unwanted disconnections happens all the time. Well, it happens with crappy servers (I have it often with MSN).
It should try to reconnect like IRC clients do.
A suggestion:
wait 30 sec to reconnect, if it still isn't working, try after 60s, then 120s, etc.
you should be able to stop the automatic reconnection with /squit of course
Updated by Romain Bignon 10 months ago
- Status changed from New to Assigned
- Priority changed from Normal to High
Yes, this is the facebook plugin which sucks.
pankkake: your solution is correct.
Updated by Romain Bignon 10 months ago
- Target version changed from 1.0-alpha to 1.1
Updated by Romain Bignon 10 months ago
- Target version changed from 1.1 to 1.0
Updated by Romain Bignon 8 months ago
- Due date set to 2009-07-08
- Status changed from Assigned to Closed
- % Done changed from 0 to 100