Follow-up to #2408371: Proxies of module interfaces don't work →
- Currently middlewares after page_cache are not proxied as the ProxyServicesPass() comes too early to find the dynamic 'lazy' definition.
Due to changes of the proxy services, we no longer have lazy middlewares which causes a bit of an overhead for page cache. This is a performance only change,
but could totally be changed afterwards
Needs work
9.5
It affects performance. It is often combined with the Needs profiling tag.
The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.
There is consensus among core maintainers that this is a major issue. Only core committers should add this tag.
Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
#36 is missing nearly all of the changes from #15 and causing thousands of test failures.
Closing this as a duplicate of 📌 [meta] Replace lazy service proxy generation with service closures Active which will change all of core's proxy classes to use service closures.
Saving credits for issue triage and other contributors.