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

FLOOD_WAIT errors are not propagated #18

Open
roboslone opened this issue Jun 21, 2017 · 2 comments
Open

FLOOD_WAIT errors are not propagated #18

roboslone opened this issue Jun 21, 2017 · 2 comments

Comments

@roboslone
Copy link

I believe the issue is missing break here.

Also, what would happen in case of 5xx error?

@BenWiederhake
Copy link
Collaborator

A few lines down:

if (strncmp (error, "FLOOD_WAIT_", 11)) {
          // …
          wait = 10;

It seems it is handled, but apparently with an insufficient wait time or something like that.

@roboslone
Copy link
Author

The thing is, tg never sends those to my wrapper (through a unix socket). But if I add that missing break and recompile I get messages with FLOOD_WAIT_ prefix in error field. That gives me total control over flood.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants