You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently all the errors from the telegram server (ones that runClietM is returned with) are consumed without any trace. It's very inconvenient to debug the bot in this setting. For the local debugging I've added:
processActionsIndefinitely botApp botEnv = forkIO . forever $do- runClientM (processActionJob botApp botEnv) (botClientEnv botEnv)
+ runClientM (processActionJob botApp botEnv) (botClientEnv botEnv) >>=\case+Right x ->pure()+Left e ->print e
That at least logs the results so it's possible to see what has gone wrong. But ideally there should be some better solution, like installing own exception handler. Also it would be nice to be able to catch such exceptions from the actions, for example if bot resends a message that could fail due to the bad markup and we want to send an totally escaped message in case of a error, or implement clever retry.
I can contribute an implementation if we agree on the design.
The text was updated successfully, but these errors were encountered:
Currently all the errors from the telegram server (ones that runClietM is returned with) are consumed without any trace. It's very inconvenient to debug the bot in this setting. For the local debugging I've added:
That at least logs the results so it's possible to see what has gone wrong. But ideally there should be some better solution, like installing own exception handler. Also it would be nice to be able to catch such exceptions from the actions, for example if bot resends a message that could fail due to the bad markup and we want to send an totally escaped message in case of a error, or implement clever retry.
I can contribute an implementation if we agree on the design.
The text was updated successfully, but these errors were encountered: