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.

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

handle tg.UpdatesTooLong to prevent client becoming unreponsive #54

Open
TrixiS opened this issue Jan 30, 2024 · 3 comments
Open

handle tg.UpdatesTooLong to prevent client becoming unreponsive #54

TrixiS opened this issue Jan 30, 2024 · 3 comments
Labels
bug Something isn't working enhancement New feature or request

Comments

@TrixiS
Copy link

TrixiS commented Jan 30, 2024

Is really needed for Dispatcher

@celestix
Copy link
Owner

Please elaborate.

@TrixiS
Copy link
Author

TrixiS commented Jan 30, 2024

After receiving UpdatesTooLong client no longer receives any updates. As I can see in dispatcher implementation, there is even no logs about receiving this update, so it's kinda confusing :) . I would like to ask for an implementation of handling UpdatesTooLong (gaps filling).

@celestix
Copy link
Owner

Can you reach us out in the support chat on telegram so that we can reduce lags between the communication? let's get it fixed.

@celestix celestix changed the title tg.UpdatesTooLong recovery handle tg.UpdatesTooLong to prevent client becoming unreponsive Feb 7, 2024
@celestix celestix added bug Something isn't working enhancement New feature or request labels Feb 7, 2024
@celestix celestix pinned this issue Feb 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants