search

sm00th / bitlbee-discord

Bitlbee plugin for Discord (http://discordapp.com)
GNU General Public License v2.0
290 stars 27 forks source link

Channel stops receiving messages #95

Open thepowersgang opened 7 years ago

thepowersgang commented 7 years ago

One of the channels I'm in has recently stopped receiving messages in bitlbee (can see new messages in the official client, but none in bitlbee until I reconnect to the bitlbee server). Channels on a different discord server appear to still be working.

I will see if I can reproduce with debug enabled.

Dav1dde commented 6 years ago

Same seems to be happening PMs, a reconnect fixes the issue. I suspect the connection times out? Anything specific I can do to try to reproduce this or help in any way?

sm00th commented 6 years ago

If you can get the debug logs (see "Debugging" section in README) that should give an idea on what is going on. How reproducible is this?

Dav1dde commented 6 years ago

Happens like 1-2 times a day for me.

sm00th commented 6 years ago

I merged a pull-request that might (so not closing the issue yet) be solving this issue. Please update your bitlbee-discord (don't forget to restart bitlbee) and see if the situation got any better. Any feedback is greatly appreciated.

Dav1dde commented 6 years ago

Thanks, I am gonna check it out when I get the time. But recently it has been reconnecting properly instead of silently losing connection.

dgw commented 6 years ago

I've had some issues with reconnecting lately and just updated from 4fc5649 to ae2177a. But if it keeps happening with the new version, I'm not quite sure if it's the same issue, so I'm posting here before opening a fresh one to avoid making a duplicate ticket.

What happens to my bitlbee-discord is, sometimes channels will be empty on reconnect but the plugin says it's logged in. I can send messages in PMs, but the channels do not have any messages or users in them. I'm not sure if incoming PMs work. Manually reconnecting fixes it, though. All I have to do is ac dc off, wait, then ac dc on, and everything connects and joins up just fine.

sm00th commented 6 years ago

All I have to do is ac dc off, wait, then ac dc on, and everything connects and joins up just fine.

If you are using autojoin - have you tried rejoining those channels by hand, i.e. closing old windows and doing /join #mychan? i've seen "empty channels" you describing with a twitter account.

Dav1dde commented 6 years ago

I haven't had this issue for a while now, seems to be fixed for me (using latest git).

Alcaro commented 6 years ago

I've seen everything die a few times, but much less often than with older versions, and only after a 'Remote host is closing websocket connection, performing soft-reconnect'.

I usually fix it with /raw quit, but ac dc off/on sounds fine too. Doesn't matter what workaround we use, none of us want to need it at all.

sm00th commented 6 years ago

Doesn't matter what workaround we use, none of us want to need it at all.

It does. Without the debug logs it is hard to tell what went wrong full reconnect starts things from scratch, whether rejoining the channel works would at least tell me if the channel_info data is properly populated when this issue occurs.

dgw commented 6 years ago

whether rejoining the channel works would at least tell me if the channel_info data is properly populated when this issue occurs.

I'll come back with this, at least, next time it happens on my end, and proceed from there.