…nsionConfigurationPass (nicolas-grekas)This PR was merged into the 3.4 branch.Discussion----------[DI] fix processing of regular parameter bags by MergeExtensionConfigurationPass| Q             | A| ------------- | ---| Branch?       | 3.4| Bug fix?      | yes| New feature?  | no| BC breaks?    | no| Deprecations? | no| Tests pass?   | yes| Fixed tickets | -| License       | MIT| Doc PR        | -Spotted in and needed by#32294Commits-------b06d000 [DI] fix processing of regular parameter bags by MergeExtensionConfigurationPass

…y providing several adapters (nicolas-grekas)This PR was merged into the 4.4 branch.Discussion----------[FrameworkBundle] Allow creating chained cache pools by providing several adapters| Q             | A| ------------- | ---| Branch?       | 4.4| Bug fix?      | no| New feature?  | yes| BC breaks?    | no| Deprecations? | no| Tests pass?   | yes| Fixed tickets | -| License       | MIT| Doc PR        | -Replaces#30984, followssymfony/symfony-docs#11813This PR allows defining several adapters for one pool. When doing so, this defines a chain pool.The benefit is that all chained pools get automatic namespace and lifetime, so things are transparent:```yamlpools:    my_chained_pool:        default_lifetime: 12        adapters:          - cache.adapter.array          - cache.adapter.filesystem          - {name: cache.adapter.redis, provider: 'redis://foo'}```(see fixtures for example of PHP/XML config)/cc@Nyholm@pborreli FYICommits-------29ba091 [FrameworkBundle] Allow creating chained cache pools by providing several adapters

…(Nyholm)This PR was submitted for the master branch but it was squashed and merged into the 4.4 branch instead (closes#11855).Discussion----------Document how to create cache pool with framework configThis is some docs forsymfony/symfony#32294I removed the "old" way of doing it because this is far better.Commits-------b0dc28f Document how to create cache pool with framework config

…che (nicolas-grekas)This PR was merged into the 5.1-dev branch.Discussion----------[Cache] Add LRU + max-lifetime capabilities to ArrayCache| Q             | A| ------------- | ---| Branch?       | master| Bug fix?      | no| New feature?  | yes| Deprecations? | no| Tickets       | Fixhttps://github.com/orgs/symfony/projects/1#card-30686676| License       | MIT| Doc PR        | -In#32294 (comment),@andrerom writes:> if you plan to expose use of ArrayAdapter to a wider audience you should probably also add the following features to it:> - max item limit to avoid reaching memory limits> - own (very low, like default 100-500ms) TTL for in-memory caching, as it's in practice stale data when used in concurrent scenarios>> If you want to be advance you can also:>> - keep track of use, and evict cache items based on that using LFU when reaching limit> - in-memory cache is domain & project specific in terms of how long it's somewhat "safe" to keep items in memory, so either describe when to use and not use on a per pool term, or allow use of pool to pass in flags to opt out of in-memory cache for cases developer knows it should be ignoredThis PR implements these suggestions, via two new constructor arguments: `$maxLifetime` and `$maxItems`.In Yaml:```yamlservices:    app.lru150_cache:        parent: cache.adapter.array        arguments:            $maxItems: 150            $maxLifetime: 0.150framework:    cache:        pools:            my_chained_pool:                adapters:                  - app.lru150_cache                  - cache.adapter.filesystem```This configuration adds a local memory cache that keeps max 150 elements for 150ms on top of a filesystem cache./cc@lyrixx since you were also interested in it.Commits-------48a5d5e [Cache] Add LRU + max-lifetime capabilities to ArrayCache

…che (nicolas-grekas)This PR was merged into the 5.1-dev branch.Discussion----------[Cache] Add LRU + max-lifetime capabilities to ArrayCache| Q             | A| ------------- | ---| Branch?       | master| Bug fix?      | no| New feature?  | yes| Deprecations? | no| Tickets       | Fixhttps://github.com/orgs/symfony/projects/1#card-30686676| License       | MIT| Doc PR        | -Insymfony/symfony#32294 (comment),@andrerom writes:> if you plan to expose use of ArrayAdapter to a wider audience you should probably also add the following features to it:> - max item limit to avoid reaching memory limits> - own (very low, like default 100-500ms) TTL for in-memory caching, as it's in practice stale data when used in concurrent scenarios>> If you want to be advance you can also:>> - keep track of use, and evict cache items based on that using LFU when reaching limit> - in-memory cache is domain & project specific in terms of how long it's somewhat "safe" to keep items in memory, so either describe when to use and not use on a per pool term, or allow use of pool to pass in flags to opt out of in-memory cache for cases developer knows it should be ignoredThis PR implements these suggestions, via two new constructor arguments: `$maxLifetime` and `$maxItems`.In Yaml:```yamlservices:    app.lru150_cache:        parent: cache.adapter.array        arguments:            $maxItems: 150            $maxLifetime: 0.150framework:    cache:        pools:            my_chained_pool:                adapters:                  - app.lru150_cache                  - cache.adapter.filesystem```This configuration adds a local memory cache that keeps max 150 elements for 150ms on top of a filesystem cache./cc@lyrixx since you were also interested in it.Commits-------48a5d5e8a9 [Cache] Add LRU + max-lifetime capabilities to ArrayCache