Invalidate Zend OPcache to ensure saved version used #102
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using an opcode cache, configuration files are cached.
So, after a configuration file is updated, its old content will be served by cached until invalidated, or checked.
With Zend Opcache, default check delay is 2"
And, it is common to have a greater value on production env.
This PR fix this (only for opcache, other opcode caches such as XCache or deprecated APC are not handled)