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
This PR was merged into the 6.4 branch.
Discussion
----------
[FrameworkBundle] Fix wiring ConsoleProfilerListener
| Q | A
| ------------- | ---
| Branch? | 6.4
| Bug fix? | yes
| New feature? | no
| Deprecations? | no
| Issues | -
| License | MIT
At the moment, when cache:clear is called, the profiler is instantiated, with all its data collectors.
When one of them needs an env var to be constructed, 💥
But this should not happen in the first place: command profiling is an opt-in feature. Nothing related should be instantiated unless asked to do so.
The issue happens because service registration doesn't take care of not using the profiler unless really needed.
This fixes it by:
1. not using the profiler to "disable" it
2. injecting a lazy profiler service so that it's instantiated only when actually required
Commits
-------
45763bd [FrameworkBundle] Fix wiring ConsoleProfilerListener
0 commit comments