You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#50253 forces the cache:clear to always run in the cache_dir, even when both build_dir and cache_dir are the same directory.
This leads to some files being deleted if the container cache is not fresh (which is always the case if the cache_dir directory was already existing and warmed up).
Since the optional CacheWarmers are run in the cache_dir, their artefacts are lost once the cache_dir is replaced with the warmup directory.
How to reproduce
s new --dir symfony_cache_dir_problem
cd ./symfony_cache_dir_problem
composer install -q
# See that router cache is warmed up
composer install -q
# See that router cache is missing
Possible Solution
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered:
…ubsequent runs (Okhoshi)
This PR was merged into the 5.4 branch.
Discussion
----------
[FrameworkBundle] Prevent `cache:clear` to lose files on subsequent runs
| Q | A
| ------------- | ---
| Branch? | 5.4
| Bug fix? | yes
| New feature? | no
| Deprecations? | no
| Tickets | Fix#50474
| License | MIT
| Doc PR | N/A
See #50474 for the details and reproduction information.
Commits
-------
61bdd80 [FrameworkBundle] Prevent `cache:clear` to lose files on subsequent runs
Symfony version(s) affected
5.4.24,6.2.11
Description
#50253 forces the
cache:clear
to always run in thecache_dir
, even when bothbuild_dir
andcache_dir
are the same directory.This leads to some files being deleted if the container cache is not fresh (which is always the case if the
cache_dir
directory was already existing and warmed up).Since the optional CacheWarmers are run in the
cache_dir
, their artefacts are lost once thecache_dir
is replaced with the warmup directory.How to reproduce
Possible Solution
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: