Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

[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

Merged

Conversation

@AydinHassan
Copy link
Contributor

@AydinHassanAydinHassan commentedOct 3, 2025
edited by nicolas-grekas
Loading

QA
Branch?7.3
Bug fix?yes
New feature?no
Deprecations?no
Issuesn/a
LicenseMIT

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 becauseusedEnvs is 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.

@AydinHassan
Copy link
ContributorAuthor

AydinHassan commentedOct 3, 2025
edited
Loading

@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?

@nicolas-grekas
Copy link
Member

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!

@AydinHassan
Copy link
ContributorAuthor

@nicolas-grekas we could certainly apply the fix to 6.4, but since the result of$usedEnvs is not used anywhere, I don't know how we could test that, effectively there is no change of behaviour with or without the fix in 6.4, at least I can't see.

Only in 7.2 where the new if condition is added can we use my test.

@nicolas-grekas
Copy link
Member

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?

@nicolas-grekasnicolas-grekas modified the milestones:6.4,7.3Oct 3, 2025
@AydinHassanAydinHassan changed the base branch from6.4 to7.3October 3, 2025 15:49
@AydinHassan
Copy link
ContributorAuthor

no problem! and done :)

@nicolas-grekas
Copy link
Member

Thank you@AydinHassan.

AydinHassan reacted with heart emojiAydinHassan reacted with rocket emoji

@nicolas-grekasnicolas-grekas merged commit0b12ec2 intosymfony:7.3Oct 6, 2025
14 of 22 checks passed
@AydinHassanAydinHassan deleted the lock-from-service-fix branchOctober 6, 2025 15:34
@fabpotfabpot mentioned this pull requestOct 28, 2025
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@lyrixxlyrixxAwaiting requested review from lyrixx

@ycerutoycerutoAwaiting requested review from yceruto

@chalasrchalasrAwaiting requested review from chalasr

@dunglasdunglasAwaiting requested review from dunglas

@OskarStarkOskarStarkAwaiting requested review from OskarStark

@jderussejderusseAwaiting requested review from jderusse

@xabbuhxabbuhAwaiting requested review from xabbuh

Assignees

No one assigned

Projects

None yet

Milestone

7.3

Development

Successfully merging this pull request may close these issues.

3 participants

@AydinHassan@nicolas-grekas@carsonbot

[8]ページ先頭

©2009-2025 Movatter.jp