We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
exit_code
I have the following task:
#[AsTask(name: 'twig-cs-fixer')] function twigcsfixer( #[AsOption(mode: InputOption::VALUE_NEGATABLE)] bool $fix = true, ): int { if ( ! fs()->exists('vendor')) { composer_install(); } return exit_code(sprintf('vendor/bin/twig-cs-fixer %s', $fix ? 'fix' : 'check')); }
I noticed for a long time now, that the output sometimes gets corrupted when the output is a bit longer than let's say 20 lines.
I always thought it was my new terminal Ghostty or my custom PHPStan error formatter.
But today, I noticed the same problem in PHPStorm's terminal and with another program: Twig CS Fixer.
I have the feeling this is because the stdout and stderr are writing over each other together with terminal coloring.
It doesn't always happen. Sometimes, it resolves itself after a few runs (indicating it's a timing issue).
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I have the following task:
I noticed for a long time now, that the output sometimes gets corrupted when the output is a bit longer than let's say 20 lines.
I always thought it was my new terminal Ghostty or my custom PHPStan error formatter.
But today, I noticed the same problem in PHPStorm's terminal and with another program: Twig CS Fixer.
I have the feeling this is because the stdout and stderr are writing over each other together with terminal coloring.
It doesn't always happen. Sometimes, it resolves itself after a few runs (indicating it's a timing issue).
The text was updated successfully, but these errors were encountered: