TW

@fantasya-pbem Well, my impression was that there definitely is some interest (see also misc. other related tickets) and I was primarily waiting for you to finish your work, see https://github.com/borgbackup/borg/issues/6756#issuecomment-1159068059...

**Yes, we can just leave warnings away for now to simplify the task.** So, only error return codes for conditions that lead to a rather immediate termination. Usually this means...

@LocutusOfBorg I'ld like to release 1.2.2 soon to get some fixes out, esp. the regression seen in 1.2.1. Not sure whether to merge this PR (and backport it to 1.2)...

Guess it should work: https://github.com/pypa/setuptools_scm/commit/b45e19f9f275a31873fd5e07faabef16fd0bbec0#diff-bdefa0298003efada7c465428643cc6d9c129168afb3eb5c551b40fcc77feac1L39 - i don't see the trailing blank in the removed template lines - there is also the LF at the end in the removed template...

@LocutusOfBorg i already merged this change into master (so it is already in 2.0.0b1 release), but would like to wait for your feedback before merging into 1.2-maint.

closing this, accidentally did this against master instead of against 1.2-maint.

About the question in the commit comment about longer "user time" when running multithreaded compare to single-threaded: The answer might be that this was a dual core cpu with hyperthreading....

Some things are TODO there: - remote repo tests are broken (and thus currently disabled) - that delayer thread is strange, better solution? - likely AES counter uniqueness is broken...

Interesting idea. Can you say what the pros of this approach are compared to Python's Queue module (which is in stdlib and threadsafe)? The Queue module is what the multithreading...

@schuft69 please see the ticket about compression about why this is not that simple in case of borg.