-
-
Notifications
You must be signed in to change notification settings - Fork 147
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
If bot is blocked by user infinite app crash and flood happens #65
Comments
Seems like similar to #55 will try to update to 2.0.1 |
Pulled v.2.0.1 got:
|
So I've added to my config: -- missing lines and ff4e7aa#diff-433b0f9eaf8520c5f8a1595f1572c062086d52740d3ab5554e52c653dabd5c07R1 --config/strings file, that were added from v.2.0.0 but @bostrot I suppose App shouldn't crash if some if config lines are absent. You broke backward compatibility with patch version v2.0.0->v.2.0.1. That shoud be treated as v3.0.0 in that case. Or better to remove depencies from unneeded/unsused config lines. |
And still after all magic I got:
|
And tsc shows:
|
I agree. About the docker error: Seems like there is a Node version mismatch. Can you try using Node v14 for the docker image while building? Also the latest image should be up on docker hub so try using that and see if that works (bostrot/telegram-support-bot:latest). |
Closing as it seems it was fixed by that. |
Finally got it working on Node v14.17.5. But still:
|
Can't reproduce that it doesn't work on Node v10 v12. What specific version did you use? |
Describe the bug
Bad error and reptry handling.
To Reproduce
Steps to reproduce the behavior:
! No messages from Telegrams getUpdates queue will be flushed, so they will be received again and again.
Expected behavior
Screenshots
The text was updated successfully, but these errors were encountered: