Dave Vasilevsky
Dave Vasilevsky
Thanks for the report. Can I get some more details? The specific commit that you're working off of, and the OS and platform that you're using, could at least help...
Oh, also which compressed format you're using would be good to know.
Something like that ought to be possible, but a bit complicated. You'd need to truncate, append the data, and then rewrite the index.
Oh, the index _does_ go near the end! A pixz file with 3 data blocks looks like this: 1. XZ stream header 2. Data block 1 3. Data block 2...
As mentioned above, there's actually _two_ indexes in a pixz file: The XZ index, and the pixz tar file index. You can read about the XZ index in the link...
pixz's tar-mode uses (abuses?) the fact that tar-files always end with a couple of blocks full of zeros, and tar ignores anything after it. So pixz's index can just go...
Do you know in advance how much RAM and how many cores the system has? You could also try adjusting the compression level, as well as using -q/-f to tune...
That looks correct! Not sure what's wrong with CI though.
Yeah, the CI failure is real, I can reproduce with `make check` locally. Can you?
Is 7z a filter compressor (like pixz, gzip, ztsd...) or an archive format (like zip?) If the latter, I'm not sure it makes sense to attempt to compare directly.