Théo FIDRY

>For a better readability on extension report used (sort results by type column) is it really better to sort by source rather than extension? Because if you want to evaluate...

>And the best one will be to add, as I've already https://github.com/box-project/box/issues/1237#issuecomment-1855405844, the note about zlib usage. I'll rename it to `phar-compression` instead of root, but I wouldn't use the...

@pdvnl could you check if you have the zlib extension? Your error is _really_ weird. I cannot reproduce it and also the whole pipeline would have completely failed

Does the issue still appears with the latest version?

I think I found the issue, the offending code is: ```php enum CompressionAlgorithm : int { case GZ = Phar::GZ; case BZ2 = Phar::BZ2; case NONE = Phar::NONE; } ```...

Investigating this some more, I cannot reproduce. Having the following PHP script: ```php

Ha ok this is quite helpful. Re-opening this as it likely means: 1. There is a way to reproduce it 2. This is preventable >Which allowed the compilation to proceed....

Could there be that a mbstring poly fill is present? Thanks to the composer.lock file we remove all the covered extension requirements

>Extension zlib is shown as a root definition, while it's not the case in PHPBench composer.json Probably from: ``` Files Compression: GZ ``` If it's GZ-compressed it requires `ext-zlib`. Currently...

@llaville do you think it would be good enough to show this as part of a command rather than the info? The difference would be that you compute the requirements...