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
I've noticed that the lock acquisition process in the DynamoDBStore class seems to apply a duplicate prefix when using DynamoDB as the cache driver.
Specifically, the DynamoDBStore->add method already adds the prefix, and then the DynamoDBStore->lock method adds the prefix again, which leads to redundancy.
As Laravel is an open source project, we rely on the community to help us diagnose and fix issues as it is not possible to research and fix every issue reported to us via GitHub.
If possible, please make a pull request fixing the issue you have described, along with corresponding tests. All pull requests are promptly reviewed by the Laravel team.
Close#52954
This PR remove the duplicated prefix when use DynamoDB as cache drive and try to lock
DynamoDB Key now:
laravel_cache_laravel_cache_my-lock
DynamoDB Key after:
laravel_cache_my-lock
Laravel Version
11
PHP Version
8.3
Database Driver & Version
No response
Description
Hi team,
I've noticed that the lock acquisition process in the DynamoDBStore class seems to apply a duplicate prefix when using DynamoDB as the cache driver.
Specifically, the DynamoDBStore->add method already adds the prefix, and then the DynamoDBStore->lock method adds the prefix again, which leads to redundancy.
You can view the relevant line here:
https://github.com/laravel/framework/blame/0d7842256c3441aef0aa3408a704c62096405090/src/Illuminate/Cache/DynamoDbStore.php#L415
Thanks
Steps To Reproduce
Run this code:
DynamoDB Key will be:
laravel_cache_laravel_cache_my-lock
It should be:
laravel_cache_my-lock
The text was updated successfully, but these errors were encountered: