Skip to content
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The following requested cache types are not supported: 'compiled_config'. #11295

Closed
AntonEvers opened this issue Oct 8, 2017 · 3 comments
Closed
Assignees
Labels
Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release

Comments

@AntonEvers
Copy link
Contributor

AntonEvers commented Oct 8, 2017

compiled_config is the only subclass of \Magento\Framework\Cache\Frontend\Decorator\TagScope that does not appear in any cache.xml file. Thus the bin/magento cache:... commands do not know about it. You cannot flush or clean it, neither can you enable/disable the compiled_config cache. However it does appear in app/etc/env.php as seen in #4556 (comment) and #4853 (comment) and #5223 (comment) among others.

Preconditions

  1. Magento 2.1.9
  2. Magento 2.2-develop

Steps to reproduce

  1. Run bin/magento cache:enable compiled_config

Expected result

Changed cache status:
               compiled_config: 0 -> 1
Cleaned cache types:
compiled_config

Actual result (2.1.9)


  [InvalidArgumentException]
  The following requested cache types are not supported: 'compiled_config'.
  Supported types: config, layout, block_html, collections, reflection, db_ddl, eav, customer_notification, translate, target_rule, full_page, config_integration, config_integration_api, config_webservice



cache:enable [--bootstrap="..."] [types1] ... [typesN]

Actual result (2.2-develop)


  [InvalidArgumentException]
  The following requested cache types are not supported: 'compiled_config'.
  Supported types: config, layout, block_html, collections, reflection, db_ddl, eav, customer_notification, config_integration, config_integration_api, full_page, translate, config_webservice


cache:enable [--bootstrap BOOTSTRAP] [--] [<types>]...
@magento-engcom-team magento-engcom-team added the Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed label Oct 8, 2017
AntonEvers pushed a commit to AntonEvers/magento2 that referenced this issue Oct 8, 2017
This seems to be missing as it is the only subclass of `\Magento\Framework\Cache\Frontend\Decorator\TagScope` that does not appear in any `cache.xml` file.

Fixes magento#11295
@dmanners dmanners added Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release labels Oct 9, 2017
@magento-engcom-team
Copy link
Contributor

@ajpevers, thank you for your report.
We've created internal ticket(s) MAGETWO-81420 to track progress on the issue.

@magento-engcom-team magento-engcom-team added 2.1.x Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release labels Oct 11, 2017
@magento-team
Copy link
Contributor

Internal ticket to track issue progress: MAGETWO-81276

@AntonEvers
Copy link
Contributor Author

In M2.3.1:

bin/magento cache:enable compiled_config
Changed cache status:
               compiled_config: 0 -> 1
Cleaned cache types:
compiled_config

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release
Projects
None yet
Development

No branches or pull requests

5 participants