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.

Sign up for GitHub

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

Jump to bottom

Disconnecting not always detected #13

Closed
TemeV opened this issue Dec 13, 2015 · 3 comments
Closed

Disconnecting not always detected #13

TemeV opened this issue Dec 13, 2015 · 3 comments

Comments

@TemeV
Copy link
Contributor

TemeV commented Dec 13, 2015

CTelegramDispatcher::whenConnectionStatusChanged doesn't seem to do anything when disconnecting happens and reason is not ConnectionStatusReasonTimeout.
I had this in my log:

void CTelegramDispatcher::whenConnectionStatusChanged(int, int, quint32) status 0 reason 0 dc 2

After that Morse was still "online" but did not receive any messages. Switching Morse to offline and back online got the messages flowing again.
@Kaffeine
Copy link
Owner

Indeed. I'm going to fix this. Thanks!

@Kaffeine
Copy link
Owner

I think I fixed the issue via commit 78ca5c6.

@TemeV
Copy link
Contributor Author

TemeV commented Dec 13, 2015

I think that should fix it, but I don't really know how to reproduce the issue though.

@TemeV TemeV closed this as completed Dec 13, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Kaffeine @TemeV