You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I have Xdebug 3 enabled (xdebug.mode=debug, xdebug.start_with_request=yes), but no listening client for it, PHP emits this message to stderr:
Xdebug: [Step Debug] Could not connect to debugging client. Tried: 10.254.254.254:9003 (through xdebug.client_host/xdebug.client_port) :-(
That causes linter to crash with following output:
$ vendor/bin/parallel-lint -e php src tests
Xdebug: [Step Debug] Could not connect to debugging client. Tried: 10.254.254.254:9003 (through xdebug.client_host/xdebug.client_port) :-(
PHP 7.3.26 | 10 parallel jobs
............................................................ 60/124 (48 %)
.........................................................Error in skip-linting.php process
Error output: Xdebug: [Step Debug] Could not connect to debugging client. Tried: 10.254.254.254:9003 (through xdebug.client_host/xdebug.client_port) :-(
Investigating the issue I found this code snippet in ParallelLint.php:
if ($skipLintProcess->getErrorOutput()) {
$message = "Error in skip-linting.php process\nError output: {$skipLintProcess->getErrorOutput()}";
thrownew \Exception($message);
}
Why is process error determined by stderr content instead of status code of the process? I am adding PR to change that, but maybe there is some reason for this?
The text was updated successfully, but these errors were encountered:
When I have Xdebug 3 enabled (
xdebug.mode=debug, xdebug.start_with_request=yes
), but no listening client for it, PHP emits this message to stderr:That causes linter to crash with following output:
Investigating the issue I found this code snippet in
ParallelLint.php
:Why is process error determined by stderr content instead of status code of the process? I am adding PR to change that, but maybe there is some reason for this?
The text was updated successfully, but these errors were encountered: