-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
Cache component problem #19912
New issue
Have a question about this project? 8000 strong> 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
Comments
Do you run your command in the same environment (prod/dev) as you use in the browser? |
@jakzal , in the same dev environment. I doublechecked that. |
@vudaltsov would you mind forking Symfony Standard edition and reproducing your problem on a new branch please? We need to isolate this problem with simplest possible code. |
I reproduced the problem in the clean fork of the project, but everything worked. Sorry for this incorrect issue. |
@jakzal, I am digging into the problem in my actual project. I noticed that when I run warmup command right after the cache clear command, it creates cache in a different place than if I run my command after I once visit any project page in the browser. What finally solved the issue was commenting the |
@nicolas-grekas, could you, please, help with this? |
What are you using as your system environment (docker / no container / vagrant) ? |
@Simperfit, no container. Just directly on Ubuntu I am working on. |
Should be fixed by #20147 |
…name in cache:clear command (nicolas-grekas) This PR was merged into the 2.7 branch. Discussion ---------- [FrameworkBundle] Alter container class instead of kernel name in cache:clear command | Q | A | ------------- | --- | Branch? | 2.7 | Bug fix? | yes | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | #19912 | License | MIT | Doc PR | - The decision to alter kernel's name instead of the container's class dates from cc3a40e But this is causing issues such as #19912. Looking more carefully, the real intent is to change the container class and there is no need to alter also the kernel's name at this stage. Commits ------- 73c9693 [FrameworkBundle] Alter container class instead of kernel name in cache:clear command
Symfony 3.1
cache:clear
$cacheItem->isHit = false
Working scenario:
cache:clear
$cacheItem->isHit = true
and everything works fineSo, it looks like running the cache warm-up command right after the cache:clear command doesn't make sense. Is this the expected behaviour?
The text was updated successfully, but these errors were encountered: