create --progress no longer shows each file processed since v1.3.6 #221

Closed
opened 2019-09-25 18:03:33 +00:00 by mattbuff-nynhp · 5 comments

What I'm trying to do and why

Trying to see each file processed, whether or not is has been modified. This output is useful for monitoring progress on long running backups with large numbers of unmodified files.

Steps to reproduce (if a bug)

sudo borgmatic create --progress -c /etc/borgmatic.d/example.yaml

Actual behavior (if a bug)

In versions 1.3.6 - 1.3.19, only added, deleted, or modified files are shown.

Expected behavior (if a bug)

In borgmatic version 1.3.5, all files are shown when issuing the --progress argument.

Environment

borgmatic version: 1.3.19

borgmatic installation method: pip

Borg version: 1.1.9

Python version: 3.5.3

operating system and version: Debian 9 (Stretch)

#### What I'm trying to do and why Trying to see each file processed, whether or not is has been modified. This output is useful for monitoring progress on long running backups with large numbers of unmodified files. #### Steps to reproduce (if a bug) sudo borgmatic create --progress -c /etc/borgmatic.d/example.yaml #### Actual behavior (if a bug) In versions 1.3.6 - 1.3.19, only added, deleted, or modified files are shown. #### Expected behavior (if a bug) In borgmatic version 1.3.5, all files are shown when issuing the --progress argument. #### Environment **borgmatic version:** 1.3.19 **borgmatic installation method:** pip **Borg version:** 1.1.9 **Python version:** 3.5.3 **operating system and version:** Debian 9 (Stretch)
Owner

Thanks for filing this! I've confirmed the same behavior locally. I'm looking into it.

Thanks for filing this! I've confirmed the same behavior locally. I'm looking into it.
witten added the
bug
label 2019-09-25 18:10:14 +00:00
Owner

Looks like the logging changes that you've helpfully pinpointed to 1.3.6 made all (well, most) Borg output get slurped into the logging system instead of going directly to stdout/stderr. This prevented real-time --progress output from showing up at the console.

What I can do is add an exception for --progress so that when it's used, it'll bypass logging and spew directly to the console like it used to. The side effect is that --progress and --syslog-verbosity won't be usable together.

Looks like the logging changes that you've helpfully pinpointed to 1.3.6 made all (well, most) Borg output get slurped into the logging system instead of going directly to stdout/stderr. This prevented real-time `--progress` output from showing up at the console. What I can do is add an exception for `--progress` so that when it's used, it'll bypass logging and spew directly to the console like it used to. The side effect is that `--progress` and `--syslog-verbosity` won't be usable together.
Owner

Okay, this should be fixed now in borgmatic 1.3.20, just released. Let me know if you experience any other problems or regressions. Thanks again for reporting!

Okay, this should be fixed now in borgmatic 1.3.20, just released. Let me know if you experience any other problems or regressions. Thanks again for reporting!
Author

Confirmed that it's now working. Having --progress and --syslog-verbosity be mutually exclusive makes perfect sense. Thank you!

Confirmed that it's now working. Having `--progress` and `--syslog-verbosity` be mutually exclusive makes perfect sense. Thank you!
Owner

Glad to hear it!

Glad to hear it!
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#221
No description provided.