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

Investigate lag #12

Open
EvanKnowles opened this issue Nov 30, 2018 · 7 comments
Open

Investigate lag #12

EvanKnowles opened this issue Nov 30, 2018 · 7 comments
Labels
bug Something isn't working

Comments

@EvanKnowles
Copy link
Owner

No description provided.

@dagwud dagwud closed this as completed Dec 1, 2018
@dagwud dagwud reopened this Dec 1, 2018
@dagwud
Copy link
Collaborator

dagwud commented Dec 1, 2018

Whoops - sorry, wrong button - accidentally closed prematurely

@EvanKnowles EvanKnowles added the bug Something isn't working label Dec 2, 2018
@EvanKnowles
Copy link
Owner Author

This the lag related to the object sync, the synch which kinda buggered up the game.

@EvanKnowles
Copy link
Owner Author

This not the lag related to the object sync, it's us hitting the Telegram limit.

@EvanKnowles
Copy link
Owner Author

CanDoGram fixed to respect rate limitations, should fix this.

@EvanKnowles
Copy link
Owner Author

As per here, sounds like it may be a timeout on the Telegram side. Will try catching the exception, backing off for a bit and re-sending.

Maybe timeout should be shorter then?

@EvanKnowles
Copy link
Owner Author

Okay, that doesn't help at all it turns out. Catching the exception and attempting to resend just means that a bunch of the same message gets sent at the end. Swallowing the exception for now so the process isn't buggered.

@EvanKnowles
Copy link
Owner Author

It's the 20msg/min rate, not the 1/s

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants