Throw exception if the same service is injected twice in ChainedFastBackend

Created on 19 June 2016, about 9 years ago

Updated 9 September 2025, 8 days ago

Follow-up to 🐛 cache.backend.chainedfast misbehaves when both fast and consistent backends point to the same storage Fixed

Problem/Motivation

cache.backend.chainedfast misbehaves in some situations, and the entity definitions are not updated correctly.

We added a trigger_error call, as this is something may be only configured in production sites, and we don't want to break people's production sites with exceptions without them having time for detecting the issue.

Now that 🐛 cache.backend.chainedfast misbehaves when both fast and consistent backends point to the same storage Fixed is done and released, we should change that trigger_error call with a proper exception.

Steps to reproduce:

1. Append to your services.yml:

services:
  cache.backend.chainedfast:
    class: Drupal\Core\Cache\ChainedFastBackendFactory
    arguments: ['@settings', 'cache.backend.database', 'cache.backend.database']
    calls:
      - [setContainer, ['@service_container']]

2. drush cr --yes
3. Enable aggregator module.
4. You get an undefined entity exception

Proposed resolution

Throw an exception.

Remaining tasks

Write a patch.

User interface changes

None.

API changes

None.

Data model changes

None.

📌 Task

Status

Postponed: needs info

Version

11.0 🔥

Component

cache system

Created by

🇪🇸Spain penyaskito Seville 💃, Spain 🇪🇸, UTC+2 🇪🇺

Live updates comments and jobs are added and updated live.

DevDaysMilan

stale-issue-cleanup
To track issues in the developing policy for closing stale issues, [Policy, no patch] closing older issues

Incomplete comments

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment 8 days ago →
🇺🇸United States smustgrave
Thank you for creating this issue to improve Drupal.

We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024