NotificationsYou must be signed in to change notification settings
Fork9.6k
Star30.3k

[Lock] read (possible) error from Redis instance where evalSha() was called#60238

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Jump to bottom

Merged

chalasr merged 1 commit intosymfony:7.2fromxabbuh:pr-59488

Apr 17, 2025

Merged

[Lock] read (possible) error from Redis instance where evalSha() was called#60238

chalasr merged 1 commit intosymfony:7.2fromxabbuh:pr-59488

Apr 17, 2025

+1 −1

Conversation

Copy link

Member

xabbuh commentedApr 17, 2025

Q	A
Branch?	7.2
Bug fix?	yes
New feature?	no
Deprecations?	no
Issues
License	MIT

carsonbot added Status: Needs Review Bug Lock labels

Apr 17, 2025

carsonbot added this to the7.2 milestone

Apr 17, 2025

xabbuh requested a review fromjderusse as acode owner

April 17, 2025 21:01

Copy link

MemberAuthor

xabbuh commentedApr 17, 2025•
edited
Loading

I stumbled upon this issue while working on#58370. It took me a while to find the root cause as the CI currently isn't failing despite the bug that's being fixed in this PR (probably because the order in which tests are executed matters). That's why I split the PR into three commits (we can still squash them while merging though):

reduce the CI config for the Windows job to showcase thatthe tests actually fail without the fix
the fix being applied with restoring the original config to show that the patch doesindeed fix the issue
restoring the CI config to the previous state