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
bug #44669 [Cache] disable lock on CLI (nicolas-grekas)
This PR was merged into the 4.4 branch.
Discussion
----------
[Cache] disable lock on CLI
| Q | A
| ------------- | ---
| Branch? | 5.4
| Bug fix? | yes
| New feature? | no
| Deprecations? |
| Tickets | Fix #41130
| License | MIT
| Doc PR | -
I thought using semaphores would fix the linked issue but I'm proposing to revert them in #44667
Instead, I think we should disable the lock on CLI processes.
The purpose of having locks enabled by default is to prevent cache stamped at deploy time. Disabling the lock on CLI still provides this protection on eg FPM.
For ppl that really want a lock between eg crons and FPM, the lock component should be used instead.
Commits
-------
b968514286 [Cache] disable lock on CLI
0 commit comments