"ANSWER:borgmatic.execute:" prefix in cron output #863

Closed
opened 2024-05-11 11:28:17 +00:00 by ndi123 · 1 comment

What I'm trying to do and why

I run my backup via cronjob and use the following command: borgmatic --stats -c /etc/borgmatic/config.yaml

I send myself the output of the command by e-mail. In the current version of borgmatic "ANSWER:borgmatic.execute:" is added as a prefix to each line in this output.

The only reference to this issue I could find here: #835 (comment)

I added "-nc" to the command and/or "color: false" to the configuration without any change in behavior.

Steps to reproduce

No response

Actual behavior

No response

Expected behavior

No response

Other notes / implementation ideas

No response

borgmatic version

1.8.11

borgmatic installation method

pip

Borg version

1.2.8

Python version

3.9.2

Database version (if applicable)

No response

Operating system and version

Debian 11

### What I'm trying to do and why I run my backup via cronjob and use the following command: borgmatic --stats -c /etc/borgmatic/config.yaml I send myself the output of the command by e-mail. In the current version of borgmatic "ANSWER:borgmatic.execute:" is added as a prefix to each line in this output. The only reference to this issue I could find here: https://projects.torsion.org/borgmatic-collective/borgmatic/issues/835#issuecomment-7951 I added "-nc" to the command and/or "color: false" to the configuration without any change in behavior. ### Steps to reproduce _No response_ ### Actual behavior _No response_ ### Expected behavior _No response_ ### Other notes / implementation ideas _No response_ ### borgmatic version 1.8.11 ### borgmatic installation method pip ### Borg version 1.2.8 ### Python version 3.9.2 ### Database version (if applicable) _No response_ ### Operating system and version Debian 11
Owner

Thanks for bringing this to my attention! This change has been implemented in main and will be part of the next release!

(What was going on is that when color output was disabled, borgmatic was defaulting to Python's default log formatter, which apparently prefixes each log entry with the log level among other things. Now, the default formatter is no longer used.)

Thanks for bringing this to my attention! This change has been implemented in main and will be part of the next release! (What was going on is that when color output was disabled, borgmatic was defaulting to Python's default log formatter, which apparently prefixes each log entry with the log level among other things. Now, the default formatter is no longer used.)
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: borgmatic-collective/borgmatic#863
No description provided.