Closed evilsneer closed 6 years ago
fixed it by adding timeout opts to p/start
like this
(<!! (p/start token handler {:timeout 30}))
For some reason, telegram's API was not as precise with time and doubled timeout happened before morse gets a response from telegram.
I've bumped timeout for hack ten times and released a quick fix as [morse "0.3.6"]
after switching on 0.3.4 version for handling 502 error i've got an another frustrating bug
i've just strarted pooling as
(<!! (p/start token handler))
please help=)