Greg Korba

@VincentLanglet looks interesting. Basically you would like to enforce what's at the top and what's at the bottom, and the rest in the middle in the exact same order as...

Alright, at this point only 2 classes don't have tests (`Process` and `WorkerCommand`), I need to figure out if it's possible to cover them (in PHPStan both don't have tests)....

OUTDATED! It was reworked, info [here](https://github.com/PHP-CS-Fixer/PHP-CS-Fixer/pull/7777#issuecomment-2109111690). ----- I've added error handling. If there are unhandled exceptions or React communication errors, Fixer will print these errors and will return non-zero exit...

Thank you both @romm and @verfriemelt-dot-org for the feedback ❤️! When it comes to progress bar it is advancing when event is dispatched after file is processed, so looking at...

Debugging child processes is tricky, I did not want to include debug mode at this point because PR is already big enough to be problematic for a review. Maybe I...

@mfn thank you for taking your time to test this ❤️! I believe that there is I/O overhead for consequent runs as Fixer reads/writes the cache file. To compare sequential...

@romm @verfriemelt-dot-org @mfn would you be so kind and re-verify the parallel runner on your codebases? Memory usage fix apparently improves also analysis time even 2.5x comparing to what you...

@VincentLanglet Yes, please 🙂. You can link [your comment](https://github.com/PHP-CS-Fixer/PHP-CS-Fixer/pull/7395#issuecomment-2085038419) in the issue form (instead of discussion).

> It might be interessting to look into a worst case, like when cs-fixer needs to adjust most/all files Benchmark for GetResponse was done with `@PER-CS2.0` ruleset which is _not_...

Parallel with 7 CPU: > Found 8325 of 31828 files that can be fixed in 75.879 seconds, 58.000 MB memory used Sequential: > Found 8327 of 31828 files that can...