TW
Any progress here? As this is a low-level change, I'ld rather like to have this merged before releasing a 1.2 release-candidate.
Also, tests are failing in a strange way - maybe rebase on current master and force-push to trigger a new test run?
BTW, I have only 1 ticket (#5679) left for next milestone (which is 1.2.0rc1). After rc1, I would not like to add any low-level changes, so this PR would have...
Well, my timing also came out differently than expected. But the current idea is to get 1.2 out at twos-day (tuesday 2022-02-22). So if this can be updated / fixed,...
I'ld try a rebase on current master now (if you don't mind) to see if the test failures still happen after that. Currently, one can't even see why they were...
Rebased without any conflicts, so let's see what CI says...
CI looking better now.
Please do not add more features here. Blocking here is the evaluation of performance / resource usage of the existing proposed changes (== assuring there is no regression).
to simplify getting the size, for the `ObfuscatedSize` type chunks this would mean to prefix with the un-obfuscated-uncompressed size.
What we had in borg 1.2 is like: ``` OBFUS_HEADER = TYPE8 0x00 csize32 # the length is of the payload without the obfuscation trailer COMPR_HEADER = TYPE8 0x00 ```...