Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
[FrameworkBundle] fix using lock from service id when previous locks used env vars#61939
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
Conversation
44e7ddc tofcfd9a7CompareAydinHassan commentedOct 3, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
@nicolas-grekas I guess this test doesn't work because that feature was only added in 7.2, would you like me to do something or are you taking care? |
I'd be happy if you could have a look. To me, the issue exists on 6.4, even if it might manifest itself differently. That's why I rebased on 6.4. Thanks! |
@nicolas-grekas we could certainly apply the fix to 6.4, but since the result of Only in 7.2 where the new if condition is added can we use my test. |
OK, let's go with 7.3 then, sorry for the bad push. Can you reset --hard to that previous commit of yours and push+retarget again? |
fcfd9a7 to0cf7a9aCompareno problem! and done :) |
Thank you@AydinHassan. |
0b12ec2 intosymfony:7.3Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
When specifying multiple locks including one which references a service id, and a previous one used an env var, the service id is not converted in to a reference. This is because
usedEnvsis not reset in the loop and is passed by reference. Not sure if this is intentional or not but it looks like a mistake to me. A similar reset is donehere.