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
Some messages not buffered if client disconnects without /quit and then times out #322
Comments
|
This is why i use awaystore plugin for private messages and auto clear buffer is off. |
|
+1 for this idea. Ping timeouts are still a problem on most servers. Having a feature that saves buffer messages if a ping was not successful, is very welcome. |
|
I observe this problem in my own setup, and am concerned that it happens. It suggests that there is a code path through which a message can show up and, failing delivery to the user, be dropped on the floor. TCP socket calls will provide sufficient information to detect delivery error, so it concerns me that this is a problem at all. |
|
Since I'm using standby to "power off" the PC, I also have the issue of mIRC not telling ZNC it is quitting. What concerns me the most is that I actually missed a query and only learned of it much later. After looking into it a bit, it seems like I was missing chat history of at least 5min after putting the PC into standby. |
|
There is this pull request #598 which attempts to fix this. |
|
@Mkaysi That would not fix channels losing messages since it does not touch the channel logic. |
|
Oh sorry, I thought that message = private message. |
|
Mhh, not sure if this would fix the query side. I'll do some testing later and see if I can consistently reproduce it. |
|
I regularly observe this problem on an IRC/ZNC server that is oftenly accessed via VPN from countries where internet is not so reliable. |
|
Has any headway been made in relation to this issue? |
|
This is the solution that I've been happily using for a year: http://wiki.znc.in/Playback. Yes, it needs special support from your client, but that's not difficult to implement. |
Is this currently supported by anything else than Communi-*? |
Textual & Mobile Colloquy |
|
The OP's proposed solution would be a very welcomed feature. |
|
Assuming I'm not missing any important technical detail that would lead to issues, I agree with @caktux, as this solution would (hopefully) work with all standard clients and not require special plugins. |
|
Could this be closed based on *playbck or will this wait for it to be merged to ZNC? |
|
I'm not entirely sure if a solution to this issue should require non-standard client implementations and/or (third-party) plugins. |
|
Isn't this what the |
|
It never checks whether the actual `write(...)' call succeeded :( |
If I disconnect from znc due to an issue with my internet connection, some buffer may be lost, leading to confused conversations as someone assumes you saw their reply.
It would be nice to have an option to make znc keep a buffer of what was said between now and the last successful ping, and add that to the buffer if the client disconnects due to missing a ping, or E_CONN_RESET/other similar error.
--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/244531-some-messages-not-buffered-if-client-disconnects-without-quit-and-then-times-out?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github).The text was updated successfully, but these errors were encountered: