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
…` to be assigned to null in case `SIGTERM` constant doesn't exist (alexandre-daubois)
This PR was merged into the 6.3 branch.
Discussion
----------
[Messenger] Prevent `StopWorkerOnSignalsListener::$signals` to be assigned to null in case `SIGTERM` constant doesn't exist
| Q | A
| ------------- | ---
| Branch? | 6.3
| Bug fix? | yes
| New feature? | no
| Deprecations? | no
| Tickets | Fix#50529
| License | MIT
| Doc PR | _NA_
Prevents the non-nullable property to be assigned to null 🙂
Commits
-------
538a9ab [Messenger] Prevent `StopWorkerOnSignalsListener::$signals` to be assigned to null in case `SIGTERM` constant doesn't exist
Symfony version(s) affected
6.3.0
Description
We get in our pipeline the following error:
It seems like when
SIGTERM
is not defined it assigns null to the typed array property.How to reproduce
SIGTERM
constant (Don't having installed php extension)StopWorkerOnSignalsListener
Possible Solution
Check for that constant and throw error when not existing
Additional Context
No response
The text was updated successfully, but these errors were encountered: