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] Add conflict withWebProfilerBundle < 6.4#52218
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
Uh oh!
There was an error while loading.Please reload this page.
Conversation
HeahDude commentedOct 21, 2023
| Q | A |
|---|---|
| Branch? | 6.4 |
| Bug fix? | yes |
| New feature? | no |
| Deprecations? | no |
| Issues | #52210 |
| License | MIT |
nicolas-grekas commentedOct 21, 2023
Works for me, but can you think of any other way that wouldn't involve a conflict? |
HeahDude commentedOct 21, 2023 • 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.
The only other way I can think of would be to disallow FWB 6.4 by adding the conflict in WPB 5.4. |
smnandre commentedOct 21, 2023
If the problem happen only with 2 datacollectors, would it be possible to add a specific conflict ? FMB 6.4 has a conflict with worflow < 6.4, but allow console 5.4.. so i guess there won't be a problem with the new worflow profiler What if we add a conflict on console < 6.4 on FMB ? |
nicolas-grekas left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
On closer look, this is fine to me 🚀
nicolas-grekas commentedOct 21, 2023
Thank you@HeahDude. |
chalasr commentedOct 21, 2023
@smnandre That wouldn’t have been enough to fix the issue at hand as the missing template is both located in and rendered by WPB. See the failing build which does run with Console v6.4-dev |
smnandre commentedOct 21, 2023
I "fixed" it in another way..... by declaring the collector separately --> Changes:6.4...smnandre:symfony:fix/console-profiler But..... is it only because this one was merged ? (even if i restored the conflict as it was before ?) 😨 |
nicolas-grekas commentedOct 21, 2023
Send the PR! :) |
…tered (smnandre)This PR was squashed before being merged into the 6.4 branch.Discussion----------[FrameworkBundle] Fix CommandDataCollector is always registered| Q | A| ------------- | ---| Branch? | 6.4| Bug fix? | yes| New feature? | no| Deprecations? | no| Issues |Fix#52210| License | MITAnother attempt at fixing#52210, allowing to revert#52218 and leave the conflict constraints untouchedCommandDataCollector was always registered, and not always removed from the container when not needed/invalid.Commits-------6e2c2ec [FrameworkBundle] Fix CommandDataCollector is always registered