PHP-CS-Fixer: [external-wrapper-only ?] Fatal error in v3.13.1 but not in v3.13.0
Bug report
Loaded config Laravel from "d:/.php-cs-fixer.php".
PHP Fatal error: Uncaught TypeError: PhpCsFixer\Console\Report\FixReport\ReportSummary::__construct(): Argument #4 ($memory) must be of type int, bool given, called in D:\Users\User\AppData\Roaming\Composer\vendor\friendsofphp\php-cs-fixer\src\Console\Command\FixCommand.php on line 318 and defined in E:\projectx\www\stage\example\example-project\vendor\friendsofphp\php-cs-fixer\src\Console\Report\FixReport\ReportSummary.php:46
Stack trace:
#0 D:\Users\User\AppData\Roaming\Composer\vendor\friendsofphp\php-cs-fixer\src\Console\Command\FixCommand.php(318): PhpCsFixer\Console\Report\FixReport\ReportSummary->__construct()
#1 D:\Users\User\AppData\Roaming\Composer\vendor\symfony\console\Command\Command.php(291): PhpCsFixer\Console\Command\FixCommand->execute()
#2 D:\Users\User\AppData\Roaming\Composer\vendor\symfony\console\Application.php(998): Symfony\Component\Console\Command\Command->run()
#3 D:\Users\User\AppData\Roaming\Composer\vendor\symfony\console\Application.php(299): Symfony\Component\Console\Application->doRunCommand()
#4 D:\Users\User\AppData\Roaming\Composer\vendor\friendsofphp\php-cs-fixer\src\Console\Application.php(94): Symfony\Component\Console\Application->doRun()
#5 D:\Users\User\AppData\Roaming\Composer\vendor\symfony\console\Application.php(171): PhpCsFixer\Console\Application->doRun()
#6 D:\Users\User\AppData\Roaming\Composer\vendor\friendsofphp\php-cs-fixer\php-cs-fixer(115): Symfony\Component\Console\Application->run()
#7 {main}
thrown in E:\projectx\www\stage\example\example-project\vendor\friendsofphp\php-cs-fixer\src\Console\Report\FixReport\ReportSummary.php on line 46
I get the above fatal error on v3.13.1, but not v3.13.0, but I’m in the middle of something, hope the above is helpful enough, otherwise will update this as I get more information.
Code snippet that reproduces the problem
On first glance, it doesn’t look like snippet related to me.
Thank you.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 15 (7 by maintainers)
@keradus yes, please bear with me, I’m working towards that and using this issue as a storage space for my findings. I’m quite tight on time and can only dig into this when the issue surfaces + my vendor repo contains info I can’t share freely. In any case, I don’t think vendor is the cause, as I removed it but the exception still surfaced.