-
-
Notifications
You must be signed in to change notification settings - Fork 133
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
Opcache clear sometimes fails with a fatal error #350
Comments
Another possibility would possibly be to add a check for |
@sylphidlw That makes a little sense, but I think the issue these users are having a lot of the time is that they DO have opcache enabled, they just have api access restrictions. That does bring up a point that I somehow spaced though, we can just directly check that opcache.restrict_api value. |
That was also a suggestion here.
So if you first checked whether or not opcache is enabled, then check the value of opcache.restrict_api for anything other than "", then disable the API functions. |
If anyone wants to take this on the recommend solution is to have it throw an error when the system is in this state. |
This line in the FileSystem driver will sometimes fail with a fatal error in environments where the opcache api is restricted using the opcache.restrict_api configuration. This issue has plagued some of the niche members of our community and has caused them to manually modify this dependency by hand.
Should we make this line
@opcache_invalidate($path, true)
instead? I think another worse option is toeval
the contents of the file instead ofinclude
.The text was updated successfully, but these errors were encountered: