-
-
Notifications
You must be signed in to change notification settings - Fork 134
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
bug: client can't recover from connection loss #1030
Comments
this is easy to reproduce if you connect an account that consists of very large groups with a large flow of messages (several chats with 1000 messages per hour will be enough) |
Hi, any news? Logs:
After received It prints |
Sorry, no news. I'll try to debug it yet another time, but not sure that will succeed. |
I'm trying to find a way to reproduce this issue.
Just closing connection does not reproduce this issue, so probably another way is needed. If anobody have ideas how to reproduce it in controlled environment (I'm using echobot started locally) I will be very happy. |
I've tried to reproduce it in #1293 using kubernetes + cilium network policy rules, but no success either. |
|
issuing same on v0.99.2 |
+, problem still exists on v0.99.2 |
+, I confirm this issue, it continues to exist on v0.99.2 :( |
+, problem still exists on v0.99.2 |
Hey, I’m aware of this issue, but it is not trivial to fix. This issue is my top priority, that’s why it is still pinned. To make this issue fixed one can:
Anyway, thank you for using gotd and keeping this issue alive 💜This will be eventually fixed by me. |
Consistent minimal bug reproduction: https://github.com/snimshchikov/gotd-bug-repro |
Logs: https://gist.github.com/ernado/a9aa2b9b8ca02f65087013b3973b6cc0
Related: #1021
Upvote & Fund
The text was updated successfully, but these errors were encountered: