[BUG] Telegram notifications fail with Message exceeds the max length

[arthar360]

Prerequisites

• I have read the troubleshooting guide

Rclone Pre-flight Checklist (if applicable)

• This issue is NOT related to rclone (skip if not using rclone)
• I have tested rclone listremotes and rclone lsd remote: on the host and they work
• I have verified the rclone config is mounted into the container
• I have restarted the container after config changes

Bug Description

Hello,

Sometimes the telegram notifications fail. Specially on retries when the message becomes long with the following error

Steps to Reproduce

1. Setup Local volume and remote S3 Repository (using seaweedfs)
2. Setup telegram alert
3. Turn off the S3 server
4. Trigger backup
5. When the backup keeps retrying to reach the repo. The message keeps getting long
6. One first or second attempt the telegram notification arrives. Eventually when there are multiple retries the message becomes long and fails.

Expected Behavior

Notifiactions should arrive. If the message is too long, there should be a mechanism to limit character before sending.

Zerobyte version / commit

0.42.0

Deployment Method

Docker Compose

Backup/Repository Context

Backup: Local
Remote: Seaweedfs (S3)

Logs / Error Messages

[nicotsx]

Thanks for reporting, will fix for next release