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
I'm not sure if this is a Symfony issue or something on my side ... but when upgrading to/from 3.2-RC2 and 3.1, I'm getting a lot of these errors:
[...]
Writing lock file
Generating autoload files
> Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::buildBootstrap
> Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::clearCache
[Symfony\Component\Debug\Exception\ContextErrorException]
Warning: Class __PHP_Incomplete_Class has no unserializer
Script Sensio\Bundle\DistributionBundle\Composer\ScriptHandler::clearCache handling
the post-update-cmd event terminated with an exception
[RuntimeException]
An error occurred when executing the "'cache:clear --no-warmup'" command:
[Symfony\Component\Debug\Exception\ContextErrorException]
Warning: Class __PHP_Incomplete_Class has no unserializer
The text was updated successfully, but these errors were encountered:
I think this happens quite often when upgrading versions. The cache files are not always backwards compatible.
The problem with cache:clear is that before clearing the cache, the cache is first used to boot the Symfony CLI. As cache is not BC, this will error. The only solution afaik is to clear the cache yourself using rm -rf var/cache/.
…nserialize() fails (nicolas-grekas)
This PR was merged into the 2.7 branch.
Discussion
----------
[Config] ConfigCache::isFresh() should return false when unserialize() fails
| Q | A
| ------------- | ---
| Branch? | 2.7
| Bug fix? | yes
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | #20654
| License | MIT
| Doc PR | -
Removes some `Warning: Class __PHP_Incomplete_Class has no unserializer` failures when clearing the cache.
Commits
-------
609245e [Config] ConfigCache::isFresh() should return false on __PHP_Incomplete_Class
I'm not sure if this is a Symfony issue or something on my side ... but when upgrading to/from 3.2-RC2 and 3.1, I'm getting a lot of these errors:
The text was updated successfully, but these errors were encountered: