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
if ($this->processInformation['signaled'] && $this->processInformation['termsig'] !== $this->latestSignal) {
thrownewRuntimeException(sprintf('The process has been signaled with signal "%s".', $this->processInformation['termsig']));
}
This would allow to catch signaled sub-process on a higher code level and retrieve the concerned process when running many, thanks to the process property of the exception.
The text was updated successfully, but these errors were encountered:
…oullivaneuh)
This PR was merged into the 4.1-dev branch.
Discussion
----------
Introduce signaled process specific exception class
| Q | A
| ------------- | ---
| Branch? | master
| Bug fix? | no
| New feature? | yes
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | #25768
| License | MIT
| Doc PR | N/A
Introduced the `ProcessSignaledException` class to properly catch signaled process errors.
I took benefit to refactor process exception with a new `ProcessRuntimeException` class.
Commits
-------
68adb3b Introduce signaled process specific exception class
As for
ProcessTimedOutException
, it would be great to have an exception when a signal has been sent to the sub-process.Basically, on this line:
symfony/src/Symfony/Component/Process/Process.php
Lines 389 to 391 in 1df45e4
This would allow to catch signaled sub-process on a higher code level and retrieve the concerned process when running many, thanks to the process property of the exception.
The text was updated successfully, but these errors were encountered: