- ๐ฎ๐ณIndia prem suthar Ahemdabad- Gujrat , Jodhpur - Rajsthan
Prem Suthar โ made their first commit to this issueโs fork.
- Status changed to Needs review
4 months ago 12:10pm 13 August 2024 - Status changed to Needs work
4 months ago 8:26pm 14 August 2024 - ๐ฎ๐นItaly apaderno Brescia, ๐ฎ๐น
Thank you for creating a merge request!
This issue has been tagged with Needs reroll because the patch needed to be re-written to use functions exposed from the APCu extension, not from the APC extension, which is no longer developed nor supported.
There are also other changes that need to be done.
For example, there is probably no need to keep a list of locks as global variable, and there is probably no need to have a shutdown callback to remove all the locks that are still not expired. APCu associates a TTL to its values; after the TTL is passed, the value is automatically purged. - Status changed to Needs review
4 months ago 5:19pm 22 August 2024 - ๐ฎ๐นItaly apaderno Brescia, ๐ฎ๐น
Actually, without editing the settings.php file, it is not possible to set a different lock back-end.
When tests are executed, Drupal core already loaded the includes/lock.inc file. Loading another file that defines the same functions contained in that file, as required to implement a lock back-end, causes errors like Cannot redeclare lock_initialize(). -
avpaderno โ
committed c387dc83 on 7.x-2.x authored by
prem suthar โ
Issue #2332725: Lock backend
-
avpaderno โ
committed c387dc83 on 7.x-2.x authored by
prem suthar โ
- ๐ฎ๐นItaly apaderno Brescia, ๐ฎ๐น
avpaderno โ changed the visibility of the branch 2332725-lock-backend-backport to hidden.
-
avpaderno โ
committed 240e38e5 on 7.x-1.x
Issue #2332725: Implement a lock backend
-
avpaderno โ
committed 240e38e5 on 7.x-1.x
- Status changed to Fixed
4 months ago 2:09pm 24 August 2024 Automatically closed - issue fixed for 2 weeks with no activity.