I've figured out why after addition of global message queue mechanism introduction all messages get sent out with 20s delay. This is caused by the 'getUpdates' times out exactly after 20s as per default module config. This patch invokes 'getUpdates' right away skipping that request from being added to the message queue hence fixing those message delivery delays.
I've figured out why after addition of global message queue mechanism introduction all messages get sent out with 20s delay. This is caused by the 'getUpdates' times out exactly after 20s as per default module config. This patch invokes 'getUpdates' right away skipping that request from being added to the message queue hence fixing those message delivery delays.
nit: I noticed there was a linting error in code, please run grunt to make sure there are no errors and build is successful, thanks!
Published as `node-telegram-api@4.1.0`
nit: I noticed there was a linting error in code, please run `grunt` to make sure there are no errors and build is successful, thanks!
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I've figured out why after addition of global message queue mechanism introduction all messages get sent out with 20s delay. This is caused by the 'getUpdates' times out exactly after 20s as per default module config. This patch invokes 'getUpdates' right away skipping that request from being added to the message queue hence fixing those message delivery delays.
That's good to know, thanks!
Published as
node-telegram-api@4.1.0nit: I noticed there was a linting error in code, please run
gruntto make sure there are no errors and build is successful, thanks!Hi, sorry, forgot that. Will do next time :), Thanks for the merge!